[
https://issues.apache.org/jira/browse/HBASE-8357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633795#comment-13633795
]
Lars Hofhansl commented on HBASE-8357:
--------------------------------------
Isn't this the same as HBASE-2611?
> current region server failover mechanism for replication can lead to stale
> region server whose left hlogs can't be replicated by other region server
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-8357
> URL: https://issues.apache.org/jira/browse/HBASE-8357
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Affects Versions: 0.94.3
> Reporter: Feng Honghua
>
> consider this scenario: rs A/B/C, A dies, B and C race to lock A to help
> replicate A's left unreplicated hlogs, B wins and successfully creates lock
> under A's znode, but before B copies A's hlog queues to its own znode, B also
> dies, and C successfully creates lock under B's znode and helps replicate B's
> own left hlogs. But A's left hlogs can't be replicated by any other rs since
> B left back a lock under A's znode and B didn't transfer A's hlog queues to
> its own znode before B dies.
--
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
