[
https://issues.apache.org/jira/browse/HBASE-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602348#comment-13602348
]
Lars Hofhansl commented on HBASE-8099:
--------------------------------------
That's fine I think. It's only an empty map (a few dozen bytes), and it's only
if there something to failover. It's just easier to read (IMHO) if you prefer
the other approach that's fine.
By the same logic we the Random could also be per failover worker, although the
Random constructor does increment an AtomicLong.
Let's get this in soon, so I can spin the next RC.
> 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-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
