Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Crash] if tx queue has reached to parity node #91

Open
rstormsf opened this issue May 24, 2018 · 5 comments
Open

[Crash] if tx queue has reached to parity node #91

rstormsf opened this issue May 24, 2018 · 5 comments

Comments

@rstormsf
Copy link
Contributor

INFO:bridge::bridge::deposit_relay: relaying 50 deposits
ERROR:bridge: ERROR CONTEXT: deposit_relay
ERROR:bridge: ERROR CONTEXT: relaying deposit to foreign
ERROR:bridge: RPC error Error { code: ServerError(-32010), message: "There are too many transactions in the queue. Your transaction was dropped due to limit. Try increasing the fee.", data: None }
Error(Rpc(Error { code: ServerError(-32010), message: "There are too many transactions in the queue. Your transaction was dropped due to limit. Try increasing the fee.", data: None }), State { next_error: None, backtrace: None })
@yrashk
Copy link
Contributor

yrashk commented May 24, 2018

What is the most preferable course of action in this case? (Considering that we don't have a persistent queue)

@rstormsf
Copy link
Contributor Author

retry sending them after a 3-5 sec

@yrashk
Copy link
Contributor

yrashk commented May 25, 2018

Should we designate a special exit for for this error so that the supervisor pauses before a restart?

@yrashk
Copy link
Contributor

yrashk commented May 29, 2018

Or would this better be served by persisting the queue of transactions?

@akolotov
Copy link
Contributor

@yrashk have you been able to reproduce this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants