Add log message when worker lock timeouts get large #18124
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is to help track down a possible, but very rare, worker deadlock that was seen on matrix.org.
In theory, you could work back from an instance of these new logs to the approximate time when the lock was obtained and focus the diagnostic efforts there.
Pull Request Checklist
EventStore
toEventWorkerStore
.".code blocks
.(run the linters)