Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1909749170.1218052724298.JavaMail.jira@brutus>
Date: Wed, 6 Aug 2008 12:58: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=12620406#action_12620406 ] 

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

IIUC, region A with key a start key of 10 and an end key of 12 will be named A,10,12.  When it splits, the lower halves new name will be A,10,11 which sorts before A,10,12.  We don't want that, right?

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