accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luis Tavarez (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4446) Add info log line in `getMonitorLock()`
Date Thu, 26 Jan 2017 13:45:24 GMT


Luis Tavarez commented on ACCUMULO-4446:

[~mjwall] as far as this issue is concerned, I think it is ready. After talking with [~elserj],
he suggested creating an abstract class (which is in ACCUMULO-4552). One thing though, is
that I branched the work from master, not from the 1.8 branch. Should I make the changes to
the 1.8 branch too? Not familiar enough with changes for different versions.

> Add info log line in `getMonitorLock()` 
> ----------------------------------------
>                 Key: ACCUMULO-4446
>                 URL:
>             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:

This message was sent by Atlassian JIRA

View raw message