HDDS-9078. Set ratis.thirdparty.io.netty.native.workdir as OZONE home temp directory #5111
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.
What changes were proposed in this pull request?
When there is noexec permission on /tmp directory, While executing ozone shell it prompts warning related to netty working directory.
/tmp/liborg_apache_ratis_thirdparty_netty_transport_native_epoll_x86_646071388068053995247.so exists but cannot be executed even when execute permissions set; check volume for "noexec" flag; use -Dorg.apache.ratis.thirdparty.io.netty.native.workdir=[path] to set native working directory separately.
In this PR moving netty working directory inside Ozone home temp directory.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9078
How was this patch tested?
Verification pending in cluster