You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Mona Chitnis (JIRA)" <ji...@apache.org> on 2014/05/27 20:56:02 UTC

[jira] [Commented] (OOZIE-1801) ZKLocksService instrumentation should say how many locks this server has

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

Mona Chitnis commented on OOZIE-1801:
-------------------------------------

+1 codewise. But curious, how do we actually benefit from knowing how many locks are held?

> ZKLocksService instrumentation should say how many locks this server has
> ------------------------------------------------------------------------
>
>                 Key: OOZIE-1801
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1801
>             Project: Oozie
>          Issue Type: Improvement
>          Components: HA
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>         Attachments: OOZIE-1801.patch
>
>
> The MemoryLocksService has a variable named "locks" under the "locks" group in the instrumentation that reports how many locks are currently acquired.  When using Oozie HA, we don't have this.  
> We shouldn't have it report the total number of locks acquired by all Oozie servers because that would require checking ZooKeeper every time we check this.  However, reporting the number of locks acquired by _this_ Oozie server should be inexpensive while still being helpful and similar to the non-HA behavior.



--
This message was sent by Atlassian JIRA
(v6.2#6252)