Deadlock logging - #4829
Merged
Merged
Conversation
klirichek
force-pushed
the
deadlock_logging
branch
from
August 21, 2026 04:54
56ccf5f to
32602dd
Compare
After fix of #3905, sockets data (connection) was left as is, but socket itself was already closed. This record was removed by timeout. Now it removed right on the next tick of netpool. It makes other visible things (like increasing mem consumption by connections) non actual.
It is implied, there are no dupes in usual replication workflow. However at edge cases it should be temporary allowed.
This is fine-tune, ruled by MANTICORE_SHUTDOWN_ALONES_DEADLINE and MANTICORE_SHUTDOWN_ALONES_POLL env.
klirichek
force-pushed
the
deadlock_logging
branch
from
August 24, 2026 03:25
c4c908b to
151de3b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.