-
Notifications
You must be signed in to change notification settings - Fork 851
More visibility to catch a sleeper #21774
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think all log messages here should also print the block info and query id, like you added for [62514]
already. This makes it possibly to connect multiple distinct log messages, which can also be on different threads, and see whether they belong to the same query and block or not.
Co-authored-by: Tobias Gödderz <tobias@arangodb.com>
For our hunt of a sleeper we add further diagnosis:
PrefetchTask::waitFor
gets a loop with a timeout andmore logging if the timeout occurs.
thread concurrently w.r.t.
execute()
and the destructor.concurrently.
This is a forward-port from 3.12.4-4 to 3.12.5, original PR:
#21742
Scope & Purpose
Checklist