You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Billy Pearson (JIRA)" <ji...@apache.org> on 2008/07/19 07:59:31 UTC

[jira] Commented: (HBASE-711) Complain if clock skew across the cluster is badly out of sync

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

Billy Pearson commented on HBASE-711:
-------------------------------------

How about we stored a variable for the skew for the region server?
Example when the region server checks in with the the master on startup and the master sends back its time and the region server stores the skew form its clock to the master clock? 
We would need to factor this skew in to the internal code that call for timestamp not sure how much work that would be but an idea.




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