hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13709) Updates to meta table server columns may be eclipsed
Date Tue, 19 May 2015 18:19:00 GMT

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

Devaraj Das commented on HBASE-13709:

Looks good to me overall. For the issue about backup master's time being behind the active
I and [~enis] did discuss this a little - if the active master persists the timestamp used
(or a monotonically increasing ID for that matter), and have the backup master read this when
it becomes active and continue using this, it should be okay.

> 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-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

This message was sent by Atlassian JIRA

View raw message