[
https://issues.apache.org/jira/browse/HBASE-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224017#comment-13224017
]
Hudson commented on HBASE-5519:
-------------------------------
Integrated in HBase-TRUNK #2673 (See
[https://builds.apache.org/job/HBase-TRUNK/2673/])
HBASE-5519 Incorrect warning in splitlogmanager (Revision 1297707)
Result = FAILURE
stack :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/SplitLogManager.java
> 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
