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

Horizon txsub endpoint should return 503 Service Unavailable when underlying Stellar-Core not synced #3550

Closed
bartekn opened this issue Apr 16, 2021 · 0 comments · Fixed by #3653
Assignees
Labels
Milestone

Comments

@bartekn
Copy link
Contributor

bartekn commented Apr 16, 2021

What version are you using?

2.1.0

What did you do?

During the SDF outage on April, 6th 2021 Horizon POST /transactions was accepting transactions and forwarding them to Stellar-Core. While Stellar-Core (maybe?) broadcasted these transactions to the network Horizon was not able to ingest ledgers (because Stellar-Core was not synced) thus it couldn't check the status of submitted transactions.

What did you expect to see?

Horizon should detect if Stellar-Core it's using for submitting transactions is synced. If not, it should return 503 Service Unavailable and do not attempt to submit transactions.

The status can be probably checked using stellarcore.Client.Info.

What did you see instead?

All valid transactions submitted during the outage were forwarded to Stellar-Core and were getting 504 Gateway Timeout.

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

Successfully merging a pull request may close this issue.

1 participant