[
https://issues.apache.org/jira/browse/HBASE-13709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549749#comment-14549749
]
Elliott Clark commented on HBASE-13709:
---------------------------------------
The other option that I've always thought would solve some of the races in meta
is to always do a check and put.
> 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 it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
