This repository has been archived by the owner on Jun 23, 2022. It is now read-only.
fix(hdfs): do not call hdfsDisconnect() after jvm exited #736
Conversation
This file contains 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
hycdong
approved these changes
Jan 22, 2021
levy5307
approved these changes
Jan 22, 2021
zhangyifan27
added a commit
to zhangyifan27/rdsn
that referenced
this pull request
Jan 26, 2021
zhangyifan27
added a commit
to zhangyifan27/rdsn
that referenced
this pull request
Jan 26, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When we kill a pegasus progress,
vm_direct_exit(int)was first called, after that we should not callhdfsDisconnect()which would try to gc jni objects. So I removedhdfsDisconnect()from the destructor, this may lead connections leaked, but I couldn't find a safe way to call it when progress terminated.