Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 20 May 2015 02:42:00 +0000 (UTC)
From: "Liu Shaohui (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12830897.1431998850000.165119.1432089720446@Atlassian.JIRA>
In-Reply-To: <JIRA.12830897.1431998850000@Atlassian.JIRA>
References: <JIRA.12830897.1431998850000@Atlassian.JIRA>
 <JIRA.12830897.1431998850656@arcas>
Subject: [jira] [Commented] (HBASE-13709) Updates to meta table server
 columns may be eclipsed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-13709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551697#comment-14551697 ] 

Liu Shaohui commented on HBASE-13709:
-------------------------------------

{quote}
Yes, this is true. However, this is still an improvement to the current approach. We are using the max or masters time and local RSs time, so the probability is smaller. I would rather do a proper fix around these issues, but it is hard to do without re-writing the whole assignment subsystem. 
{quote}
OK. Thanks [~enis]

+1 for me.


> Updates to meta table server columns may be eclipsed
> ----------------------------------------------------
>
>                 Key: HBASE-13709
>                 URL: https://issues.apache.org/jira/browse/HBASE-13709
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.1
>
>         Attachments: hbase-13709_v1.patch, hbase-13709_v1.patch
>
>
> HBASE-11536 fixes a case where on a very rare occasion, the meta updates may be processed out of order. The fix is to use the RS's timestamp for the server column in meta update, but that actually opens up a vulnerability for clock skew (see the discussions in the jira). 
> For the region replicas case, we can reproduce a problem where the server name field is eclipsed by the masters earlier update because the RS is lagging behind. However, this is not specific to replicas, but occurs more frequently with it. 
> One option that was discussed was to send the master's ts with open region RPC and use it. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)