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

Josh Elser commented on ACCUMULO-4446:
--------------------------------------

Oh crud. This was slated for older branches too.

Let me cherry-pick it back.

> 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: 2.5h
>  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)

Reply via email to