You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/06 21:49:59 UTC

[jira] [Resolved] (HBASE-5519) Incorrect warning in splitlogmanager

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

stack resolved HBASE-5519.
--------------------------

      Resolution: Fixed
        Assignee: Prakash Khemani
    Hadoop Flags: Reviewed

Committed to 0.92, 0.94 and to trunk.  This is a usability thing.
                
> Incorrect warning in splitlogmanager
> ------------------------------------
>
>                 Key: HBASE-5519
>                 URL: https://issues.apache.org/jira/browse/HBASE-5519
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Prakash Khemani
>            Assignee: Prakash Khemani
>         Attachments: 0001-HBASE-5519-Incorrect-warning-in-splitlogmanager.patch, 5519.92.txt
>
>
> because of recently added behavior - where the splitlogmanager timeout thread get's data from zk node just to check that the zk node is there ... we might have multiple watches firing without the task znode expiring.
> remove the poor warning message. (internally, there was an assert that failed in Mikhail's tests)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira