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

Naive retry in the Stellar client does not work and blocks the tx funding service if used by too many #2294

Open
robvanmieghem opened this issue Jan 20, 2021 · 2 comments
Labels
Milestone

Comments

@robvanmieghem
Copy link
Contributor

In the Stellar client, if a transfer fails, it is retried up to 5 times without looking at the error that occurred.
If it's a timeout submitting to the Stellar network this most likely will not help since the Stellar ledger has not changed yet.
On top of this, this blocks 5 slave wallets in the transaction funding service ( well, they are reused but it might interfere with others).
The option is to increase the fee to try to get it included in the current ledger or wait until another ledger becomes available, or both

@robvanmieghem robvanmieghem added this to the next milestone Jan 20, 2021
@rkhamis
Copy link
Contributor

rkhamis commented Jan 20, 2021

the transfer is retried 5 times to have the best shot at a successful deployment.
this is already a workaround because of the service unreliability.

@robvanmieghem what do you suggest instead? we already check if the service is up when we first start

@robvanmieghem
Copy link
Contributor Author

The problem is not the service, the problem is the that the Stellar ledger is probably getting full. I mentioned the options above( wait for new ledger or increase the fee). The thing is that the current retry mechanism has a very small chance of success and impacts tx funding service stability ( through already used sequence numbers when too many clients use this)

@xmonader xmonader modified the milestones: next, later Feb 10, 2021
@xmonader xmonader modified the milestones: later, 11.6 Nov 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants