-
Notifications
You must be signed in to change notification settings - Fork 379
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
TX rollback error: sql: transaction has already been committed or rolled back #2998
Comments
Is there any way to increase the verbosity of these errors ? So we can troubleshoot them ourselves. I checked our deployment and saw that |
Hi @hectorj2f I'm triaging bugs and came across this. Apologies that nobody has replied to you earlier! Are you still seeing this? Looking at the call paths, I think #3201 will make a big difference here. Removing the inner join in the SQL query in this codepath makes serving proofs significantly cheaper. If it is an option for you, I recommend migrating to a new trillian tree that is configured to be revisionless. We will cut a release next week which will include these changes, and will create trees as revisionless by default. In the meantime, you can test this by using the |
We're seeing many errors in our Trillian instance with calls to
GetEntryAndProof
andGetLatestSignedLogRoot
. Does anyone have an idea why we're seeing these warnings ? We found these warnings during a period of time under high load.The text was updated successfully, but these errors were encountered: