Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8F7CDF91D for ; Wed, 17 Apr 2013 17:39:18 +0000 (UTC) Received: (qmail 34741 invoked by uid 500); 17 Apr 2013 17:39:17 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 34702 invoked by uid 500); 17 Apr 2013 17:39:17 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 34654 invoked by uid 99); 17 Apr 2013 17:39:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Apr 2013 17:39:17 +0000 Date: Wed, 17 Apr 2013 17:39:17 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8357) current region server failover mechanism for replication can lead to stale region server whose left hlogs can't be replicated by other region server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-8357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634234#comment-13634234 ] Andrew Purtell commented on HBASE-8357: --------------------------------------- Ping [~himanshu@cloudera.com] > 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