You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Narayan Periwal (JIRA)" <ji...@apache.org> on 2016/01/14 13:02:39 UTC

[jira] [Commented] (OOZIE-2433) oozie restart required if oozie metrics to graphing tool broken

    [ https://issues.apache.org/jira/browse/OOZIE-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098031#comment-15098031 ] 

Narayan Periwal commented on OOZIE-2433:
----------------------------------------

The issue is because of not having the latest version of the dropwizard metrics dependency.
I verified that after upgrading it to 3.1.2, the above issue get resolved.

> 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
>
> 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)