-
Notifications
You must be signed in to change notification settings - Fork 588
HDDS-10564. Make Outputstream writeExecutor daemon threads. #6418
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
Change-Id: Id5a1d332f8ac93991fd52b85ad186cbc6af9630f
|
It looks like the |
Does that mean ongoing write may be dropped and data lost? |
writeExecutor was added by HDDS-10383 and is new. |
output stream should call close() which will ensure data in the buffer is flushed. |
|
Thanks @jojochuang for the patch, @xichen01 for the review. |
(cherry picked from commit 82c02d3)
) (cherry picked from commit 82c02d3)
) (cherry picked from commit 82c02d3)
(cherry picked from commit 82c02d3)
What changes were proposed in this pull request?
HDDS-10564. Make Outputstream writeExecutor daemon threads.
Please describe your PR in detail:
HDDS-10383 added new thread pools in the output stream. They should be made daemon threads so that processes don't wait for them when exiting. (The bug is in the command line which does not close FileSystem object. Nonetheless, it would still be a good idea to make these thread pools daemon)
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-10564
How was this patch tested?
Deployed on a real cluster, with HBase on Ozone, repeated the same command to verify that the command no longer hangs.