Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Sun, 26 Jan 2014 22:13:38 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12464869.1274252179823.16118.1390774418051@arcas>
In-Reply-To: <JIRA.12464869.1274252179823@arcas>
References: <JIRA.12464869.1274252179823@arcas>
Subject: [jira] [Resolved] (HBASE-2569) Improper error handling in face of
 version mismatch between the client and the server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-2569.
--------------------------

    Resolution: Unresolved

Closing as unresolved. Refers to an old version of hbase.

> Improper error handling in face of version mismatch between the client and the server
> -------------------------------------------------------------------------------------
>
>                 Key: HBASE-2569
>                 URL: https://issues.apache.org/jira/browse/HBASE-2569
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>            Reporter: Benoit Sigoure
>            Priority: Minor
>
> I use trunk, and every once in a while, when I upgrade my test instance of HBase, my clients end up in a seemingly endless loop when instantiating an {{HTable}} instance:
> {code}
> 10/05/18 23:42:46 DEBUG zookeeper.ZooKeeperWrapper: Read ZNode /hbase/root-region-server got 192.168.0.7:61322
> 10/05/18 23:42:47 DEBUG client.HConnectionManager$TableServers: Root region location changed. Sleeping.
> 10/05/18 23:42:48 DEBUG client.HConnectionManager$TableServers: Wake. Retry finding root region.
> {code}
> I'm pretty certain that the code throws an appropriate exception to complain about the version mismatch but it must be getting eaten somewhere and the code probably applies the usual retry logic instead of throwing up its hands in the air and immediately giving up, as I think it should.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)