[
https://issues.apache.org/jira/browse/HBASE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620402#action_12620402
]
Jim Kellerman commented on HBASE-711:
-------------------------------------
HRegion plays around with current time to create region names for split
children. If we named regions as I have suggested above, this will no longer be
necessary.
All the other references to System.currentTimeMillis() are used for interval
computations and so it doesn't matter if the clock is skewed or not.
> 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.
