[
https://issues.apache.org/jira/browse/HBASE-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603032#comment-13603032
]
Hudson commented on HBASE-8099:
-------------------------------
Integrated in HBase-0.94 #903 (See
[https://builds.apache.org/job/HBase-0.94/903/])
HBASE-8099 ReplicationZookeeper.copyQueuesFromRSUsingMulti should not
return any queues if it failed to execute. (Himanshu and LarsH) (Revision
1456519)
Result = FAILURE
larsh :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/replication/ReplicationZookeeper.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSourceManager.java
> ReplicationZookeeper.copyQueuesFromRSUsingMulti should not return any queues
> if it failed to execute.
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-8099
> URL: https://issues.apache.org/jira/browse/HBASE-8099
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Himanshu Vashishtha
> Priority: Blocker
> Fix For: 0.95.0, 0.98.0, 0.94.6
>
> Attachments: 8099-example.txt, HBase-8099-94.patch,
> HBase-8099-94-v2.patch, HBase-8099-94-v3.patch, HBase-8099-94-v4.patch,
> HBase-8099-trunk-2.patch, HBase-8099-trunk.patch, HBase-8099-trunk-v3.patch,
> HBase-8099-trunk-v4.patch
>
>
> We just ran into an interesting scenario. We restarted a cluster that was
> setup as a replication source.
> The stop went cleanly.
> Upon restart *all* regionservers aborted within a few seconds with variations
> of these errors:
> http://pastebin.com/3iQVuBqS
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
