hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-711) Complain if clock skew across the cluster is badly out of sync
Date Thu, 14 Aug 2008 22:53:44 GMT

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

Jim Kellerman commented on HBASE-711:
-------------------------------------

If we require all the servers to run nntpd (or equivalent) then this should largely be a non-issue
with respect to either region names or HLog names.

The only thing we might want to do is have the master examine the HServerInfo passed from
the region server in the regionServerStartup message and if HServerInfo.getStartCode() (which
is the time the region server started) is larger than some delta from the master's current
clock time, the master should throw an exception that would cause the region server to shut
down.

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


Mime
View raw message