[
https://issues.apache.org/jira/browse/OOZIE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1801:
---------------------------------
Attachment: OOZIE-1801.patch
The patch adds an AtomicLong to keep track of the current number of locks
acquired by this Oozie server and exposed it in the instrumentation. No tests,
but I verified that when I submitted a bunch of jobs the instrumentation
variable increased on the Oozie servers and then later went back to 0.
> 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)
