Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1537342652.1218822584361.JavaMail.jira@brutus>
Date: Fri, 15 Aug 2008 10:49:44 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-711) Complain if clock skew across the
 cluster is badly out of sync
In-Reply-To: <670383524.1214449845214.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-711:
-----------------------------

That'd be useful.  Maybe a warning is good enough on master side rather than a shutdown of regionserver since we *think* we're immune to clock skew at this stage.

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