[
https://issues.apache.org/jira/browse/OOZIE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010245#comment-14010245
]
Robert Kanter commented on OOZIE-1801:
--------------------------------------
It can be useful in a sort of indirect and vague way. e.g. if you consistently
see that one Oozie server has a lot of locks and others have very few, there's
probably a load problem that should be looked into. Another reason for having
it is that without HA, we have it, so this at least keeps things consistent.
> 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)
