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 Fri, 15 Aug 2008 17:45:44 GMT

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

Jim Kellerman commented on HBASE-711:

Yes, saw that. Coupled with the use of nntpd, this is largely a non-issue. However I thought
we could add something to the startup sequence in which:

> The master examines the HServerInfo passed from the region server in the regionServerStartup
> 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.

Think that is necessary? Or should we close this issue as either wontfix or invalid?

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

View raw message