[
https://issues.apache.org/jira/browse/ACCUMULO-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839698#comment-15839698
]
Michael Wall commented on ACCUMULO-4446:
----------------------------------------
[~lstav] ah, ok. Typically, I think you should work on a ticket on the oldest
branch it is assigned to. For this ticket that would be 1.7.3. When complete
against, the 1.7 branch, we can merge it up into 1.8 then master. The
alternative would be to merge it into master and then backport into 1.8 and
1.7, but I think starting at 1.7 is cleaner. This particular change would not
be too back to backport, but can you create a new PR against 1.7 and reference
https://github.com/apache/accumulo/pull/195. I'll get it merged up. Thanks man
> Add info log line in `getMonitorLock()`
> ----------------------------------------
>
> Key: ACCUMULO-4446
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4446
> Project: Accumulo
> Issue Type: Improvement
> Components: monitor
> Reporter: Srikanth Viswanathan
> Assignee: Luis Tavarez
> Priority: Trivial
> Fix For: 1.7.3, 1.8.1, 2.0.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> When the monitor starts up and hangs on acquiring the monitor lock (for
> whatever reason, perhaps there's another monitor instance already holding the
> lock), there is no suggestion in the logs that the monitor is waiting on a
> lock. An info log would be appropriate here, along with a debug line for each
> failed attempt.
> Ref:
> https://github.com/apache/accumulo/blob/master/server/monitor/src/main/java/org/apache/accumulo/monitor/Monitor.java#L601
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
