Transaction pool doesn't respect maxTransactionsPerQueue limit

[4miners]

Expected behavior

It should not allow for more transactions than set in maxTransactionsPerQueue.

Actual behavior

It allows for more transactions than the configured maxTransactionsPerQueue limit.

Steps to reproduce

Broadcast more transactions than the default limit of 5000.

Which version(s) does this affect? (Environment, OS, etc...)

2.0.0-alpha.10

[SargeKhan]

Transaction pool sets the limit of maximum transaction per queue only for the received queue for new transactions accepted by the node. For transactions which are moved moved to the received queue from other queues do not adhere to the maximum queue size. Which is the reason why we sometimes see transactions exceeding max transactions per queue.

[shuse2]

Closing due to expected behavior, and it is the same behavior as previous implementation

[4miners]

Doesn't look like the limit is respected:

Steps to reproduce:
Run, cancel, repeat QA stress test: STRESS_COUNT=1000 npm run stress:generic

You can observe that received queue keeps growing:

[4miners]

We decided to close this issue for now.