Open hectorj2f opened 1 year ago
Is there any way to increase the verbosity of these errors ? So we can troubleshoot them ourselves. I checked our deployment and saw that --tracing=true
is enabled.
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 @master
version.
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.