-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HDDS-1721 : Client Metrics are not being pushed to the configured sin… #1034
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
…k while running a hadoop command to write to Ozone.
|
/label ozone |
|
Hi @avijayanhwx |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
bharatviswa504
left a comment
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.
+1 LGTM.
As discussed offline, @avijayanhwx will write a cwiki article to document the steps.
…emote table (apache#1034) * SAMZA-2185: Added ability to expose remote store specific features in remote table * Updated based on review comments
…k while running a hadoop command to write to Ozone. (apache#1034)
…k while running a hadoop command to write to Ozone.
Metrics system needs to be initialized for the sink configs to be picked up.
Manually tested the change. After this change, if the hadoop-metrics2.properties contains properties like such, client metrics will be pushed to sink.
xceiverclientmetrics.period=10
xceiverclientmetrics.sink.<sink_name>.plugin.urls=/path/to/JAR
xceiverclientmetrics.sink.<sink_name>.interval=10