[
https://issues.apache.org/jira/browse/HBASE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622935#action_12622935
]
stack commented on HBASE-711:
-----------------------------
FYI, in case you hadn't seen it, we added this to split code a while back:
{code}
// Calculate regionid to use. Can't be less than that of parent else
// it'll insert into wrong location over in .META. table: HBASE-710.
long rid = System.currentTimeMillis();
if (rid < this.regionInfo.getRegionId()) {
LOG.warn("Clock skew; parent regions id is " +
this.regionInfo.getRegionId() + " but current time here is " + rid);
rid = this.regionInfo.getRegionId() + 1;
}
{code}
Makes it so splits always sort after parents whatever the clockskew.
> Complain if clock skew across the cluster is badly out of sync
> --------------------------------------------------------------
>
> Key: HBASE-711
> URL: https://issues.apache.org/jira/browse/HBASE-711
> Project: Hadoop HBase
> Issue Type: New Feature
> Reporter: stack
> Assignee: Jim Kellerman
> Priority: Minor
>
> hbase-710 and hbase-609 are issues where the system has broken in presence of
> clock skew over the cluster. Would be a nice service if master could flag
> very bad clock skew. Regionservers could report their local time when they
> ping the master. It could do a compare.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
