[
https://issues.apache.org/jira/browse/HBASE-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602049#comment-13602049
]
Himanshu Vashishtha commented on HBASE-8099:
--------------------------------------------
Hmm, I added the random member to the Failover worker. I just noticed that you
mentioned to add that to the RSM class rather. I don't have any strong opinion
for this. Let me know and I'll change it.
> 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.94.7
>
> Attachments: HBase-8099-94.patch, HBase-8099-94-v2.patch,
> HBase-8099-94-v3.patch, HBase-8099-trunk-2.patch, HBase-8099-trunk.patch,
> HBase-8099-trunk-v3.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
