Parity-ethereum: What does mean "In queue: Future" in the "Your local transactions"?

[bluebu]

_Before filing a new issue, please provide the following information._

I'm running:

• Which Parity version?: v1.10.0-20180119
• Which operating system?: Linux Centos 7.4
• How installed?: via installer from source
• Are you fully synchronized?: yes
• Which network are you connected to?: foundation
• Did you try to restart the node?: yes

_Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue._

When the node run about 2 hours, there are always some transactions to be shown "In queue: Future", what does it mean?
After restart, they are still "In queue: Future", will these transactions go on to be mined by other nodes?
Or does it mean these transactions are error transactions, can I delete them?

[AyushyaChitransh]

Transactions done from an account are sequentially numbered, and these sequence numbers are called nonce. When some account sends a transaction of a higher sequence number, that transaction is said to be in future.

If you want to delete those transactions, you can use parity --no-persistent-txqueue as described on ethereum.stackexchange

[bluebu]

Cool, @AyushyaChitransh!
thx for your reply, quite clear, I have solved my problem

[bittylicious]

We are finding this happening alot, often blocking many transactions afterwards. We don't specify a gas price (just leave it up to Parity) and definitely not a nonce, yet we see this regularly. Any ideas why?

[5chdn]

Nonces are a known annoyance but there is not much the client can do about this if a transaction is not mined - for instance - blocking all following transactions, this has to be watched carefully in a 2nd layer application and handled appropriately.

[Tbaut]

@bittylicious as discussed in the chat, please open a new issue as soon as you get a trace of these "stuck transactions" to see if this is a bug.