0

After I finished my single node PoA setup, I wanted to test how many TPS it can handle.

During the load testing, I noticed that the transactions have stopped mining.

Instead, I am getting "Transaction culled...." logs.

Any idea what's happening?

Culled transactions log

0

Transaction didn't get into any block, but some other tx with the same nonce got.

https://github.com/paritytech/parity-ethereum/blob/master/miner/src/pool/local_transactions.rs#L35

  • But it has stopped mining further transactions also – abed Nov 12 '18 at 16:11
  • The solution was to kill and rerun the node, but i don’t want this to happen on production – abed Nov 12 '18 at 16:12
0

There seem to be a bug in local transactions in parity,

To overcome it I have added this flag when running my node --tx-queue-per-sender 100000

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.