[ https://issues.apache.org/jira/browse/OOZIE-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098060#comment-15098060 ]
Jaydeep Vishwakarma commented on OOZIE-2433: -------------------------------------------- Verified it , It was the issue in 3.1.0 version. With 3.1.2 it is working fine. more detail can be find in : https://github.com/dropwizard/metrics/issues/669 https://github.com/dropwizard/metrics/issues/814 +1 > oozie restart required if oozie metrics to graphing tool broken > --------------------------------------------------------------- > > Key: OOZIE-2433 > URL: https://issues.apache.org/jira/browse/OOZIE-2433 > Project: Oozie > Issue Type: Bug > Reporter: Sanjeev T > Assignee: Narayan Periwal > Attachments: OOZIE-2433.patch > > > When we start oozie service it starts emitting oozie metrics, expose to the > host > * oozie.external_monitoring.address > If we have issue on the external host or service disruption for a while, the > metrics are not exposed, it requires oozie restart > * Can we avoid oozie restart, let oozie do health check and expose metrics > * Enable logging for the oozie metrics emitting to external host -- This message was sent by Atlassian JIRA (v6.3.4#6332)