-
Notifications
You must be signed in to change notification settings - Fork 9k
HDFS-17172. Support FSNamesystemLock Parameters reconfigurable #6002
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
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
Hi Sirs @Hexiaoqiao @ayushtkn @ZanderXu @tomscut Could you please help me review this pr when you have free time ? Thanks a lot~ |
c5ecc29
to
fd706d8
Compare
🎊 +1 overall
This message was automatically generated. |
@haiyang1987 Thanks for your works. I am confused why we do not enable it by default and remove to config, any performance impact? Thanks. |
Thanks Sir @Hexiaoqiao help me review it. Sir suggestion is to remove dfs.namenode.lock.detailed-metrics.enabled directly from config, with default metricsEnabled set to true ? |
@haiyang1987 thanks for reporting this. It's good to have. Patch lgtm. |
@haiyang1987 Thanks, IMO, if no performance impact, I suggest to enable it by default without any config which involve some cost to end user, what do you think about? cc @brahmareddybattula |
Sir @Hexiaoqiao Thanks review . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @haiyang1987 for your report. LGTM
Hi Sir @Hexiaoqiao Could you please help me review this pr again when you have free time ? Thanks a lot~ |
Hi @Hexiaoqiao excuse me sir. can you help me take a look at this PR when you have time? Thank you very much~ |
Hi @ayushtkn sir,can you help me take a look at this PR when you have time. |
fd706d8
to
e10a62f
Compare
🎊 +1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
+1 from my side. Try to trigger CI manually. Let's wait what it will say. |
Thanks @Hexiaoqiao for your comment. seem have some conflicts and i will fix later. |
e2a4822
to
200643e
Compare
💔 -1 overall
This message was automatically generated. |
The failed unit test seems unrelated to this PR. Committed to trunk. Thanks @haiyang1987 and @ZanderXu ! |
Thanks @Hexiaoqiao @ZanderXu @brahmareddybattula help me review and merge it. |
…he#6002). Contributed by Haiyang Hu. Reviewed-by: ZanderXu <zanderxu@apache.org> Signed-off-by: He Xiaoqiao <hexiaoqiao@apache.org>
Description of PR
https://issues.apache.org/jira/browse/HDFS-17172
For Namesystem lock some parameters such as
"dfs.namenode.lock.detailed-metrics.enabled",
"dfs.namenode.read-lock-reporting-threshold-ms",
"dfs.namenode.write-lock-reporting-threshold-ms"
we will support reconfigurable these parameters without namenode restart is convenient for us to check the metrics operation of FSNamesystemLock.