Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1953917218.1224554084385.JavaMail.jira@brutus>
Date: Mon, 20 Oct 2008 18:54:44 -0700 (PDT)
From: "Jim Kellerman (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (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:all-tabpanel ]

Jim Kellerman updated HBASE-711:
--------------------------------

    Priority: Blocker  (was: Minor)

> 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: Bug
>            Reporter: stack
>            Assignee: Jim Kellerman
>            Priority: Blocker
>             Fix For: 0.19.0
>
>
> 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.