Closed muXxer closed 7 months ago
This issue happens also with tx spams, each faucet request or a single tx is increasing conflict count in grafana dashboard. The view after faucet requests and tx spam, no conflicts
Since we have WithForkAllTransactions
set to true
in mempool, every transaction is marked as a conflict at the start.
Entire rename of "conflicting" and ConflictDAG in favor of "spend" and "SpendDAG": rehook events.
So I wrote a faucet spammer, forcing the spammer to do payouts in a loop. Works fine so far. But from all the faucet TX, 79 are successful, and 5 failed. The reason is not the indexer code, nor the faucet code. It's because the iota-core node API returns "transactionFailureReason=2" conflicting sometimes. This happens when I query for the state of the transaction immediately after I issued the block to the node. (that happens sometimes because I have an asynchonous cleanup thread in the faucet that waits on the "send lock")