Debump netty version by 1 due to ObjectCleaner bug - #1163
Merged
Conversation
The ObjectCleaner can possibly keep a process alive forever with netty 4.1.20 since it is not a daemon thread. See: netty/netty#7617 This causes initialize-cluster-metadata to hang forever. 4.1.19 doesn't have this issue, so we should drop down to that until the fix is in a release.
sijie
approved these changes
Feb 1, 2018
Member
|
retest this please |
Contributor
|
The Netty 4.0.56.Final and 4.1.21.Final released and fix this bug ObjectCleanerThread must be a deamon thread to ensure the JVM can always terminate (#7627) |
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
4 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.
The ObjectCleaner can possibly keep a process alive forever with netty
4.1.20 since it is not a daemon thread.
See: netty/netty#7617
This causes initialize-cluster-metadata to hang forever. 4.1.19
doesn't have this issue, so we should drop down to that until the fix
is in a release.