You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/06 22:44:00 UTC

[jira] [Updated] (ACCUMULO-4446) Add info log line in `getMonitorLock()`

     [ https://issues.apache.org/jira/browse/ACCUMULO-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated ACCUMULO-4446:
-------------------------------------
    Labels: pull-request-available  (was: )

> 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
>              Labels: pull-request-available
>             Fix For: 1.7.3, 1.8.1, 2.0.0
>
>          Time Spent: 8.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
(v8.3.4#803005)