[
https://issues.apache.org/jira/browse/AMBARI-25126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807032#comment-16807032
]
Hudson commented on AMBARI-25126:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-Metrics-master-Commit #20 (See
[https://builds.apache.org/job/Ambari-Metrics-master-Commit/20/])
AMBARI-25126.fix ambari-metric exception printed in namenode (#16)
(14299376+avijayanhwx:
[https://gitbox.apache.org/repos/asf?p=ambari-metrics.git&a=commit&h=a197d284c583be1a96134215d61fbfc2ec62b66c])
* (edit)
ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/availability/MetricSinkWriteShardHostnameHashingStrategy.java
> Fix "/ by zero" exception in namenode log
> -----------------------------------------
>
> Key: AMBARI-25126
> URL: https://issues.apache.org/jira/browse/AMBARI-25126
> Project: Ambari
> Issue Type: Bug
> Reporter: Shen Yinjie
> Priority: Major
> Labels: pull-request-available
> Attachments: exception.png
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When there is no metrics collector works well，"/ by zero " exception is
> printed in namenode logs ,which is throwed by
> MetricSinkWriteShardHostnamehashingStrategy#findCollectorShard()
> We should print more friendly messages instead of "/ by zero".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
