Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Parity drops transactions #8733

Closed
GeRikz opened this issue May 29, 2018 · 1 comment
Closed

Parity drops transactions #8733

GeRikz opened this issue May 29, 2018 · 1 comment
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. Z7-duplicate 🖨 Issue is a duplicate. Closer should comment with a link to the duplicate.
Milestone

Comments

@GeRikz
Copy link

GeRikz commented May 29, 2018

I'm running:
*Which Parity version?: 1.11.1
*Which operating system?
: centos 6
*How installed?: bash <(curl https://get.parity.io -Lk)
*Are you fully synchronized?
: yes
*Which network are you connected to?: ethereum
*Did you try to restart the node?
: yes

Parity is droping all transactions with error
There are too many transactions in the queue. Your transaction was dropped due to limit. Try increasing the fee.
When i add --tx-queue-size 90000 in launch options transactions goes true but i lose all peers and peers are jumping from 1/25 to 4/25 and getting out of sync. If --tx-queue-size are removed then peers keeps above 23 but not letting transactions to chain. Im using 30gwei and 21,000 gas limit to send transactions

@Tbaut Tbaut added Z7-duplicate 🖨 Issue is a duplicate. Closer should comment with a link to the duplicate. F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. labels May 30, 2018
@Tbaut Tbaut added this to the 1.12 milestone May 30, 2018
@Tbaut
Copy link
Contributor

Tbaut commented May 30, 2018

This is a duplicate of #8679 A fix has been prepared and will be introduced in the next minor version.

@Tbaut Tbaut closed this as completed May 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. Z7-duplicate 🖨 Issue is a duplicate. Closer should comment with a link to the duplicate.
Projects
None yet
Development

No branches or pull requests

2 participants