Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 28 Oct 2012 01:47:12 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1089960985.35976.1351388832297.JavaMail.jiratomcat@arcas>
In-Reply-To: <1463482472.76754.1347567668618.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-6775) Use ZK.multi when available for
 HBASE-6710 0.92/0.94 compatibility fix
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-6775:
------------------------------

Config is a bad idea IMO.  We have enough cryptic config. already.

One thought I had was that you could connect to an ensemble member that supported multi but another member might not.  If your session moves, I don't believe the client is told so you could do a multi against an older ensemble member.  This might be a bit on the exotic side (different ensemble versions is probably temporary condition while ensemble is being updated)
                
> Use ZK.multi when available for HBASE-6710 0.92/0.94 compatibility fix
> ----------------------------------------------------------------------
>
>                 Key: HBASE-6775
>                 URL: https://issues.apache.org/jira/browse/HBASE-6775
>             Project: HBase
>          Issue Type: Improvement
>          Components: Zookeeper
>    Affects Versions: 0.94.2
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>            Priority: Minor
>             Fix For: 0.94.4
>
>
> HBASE-6710 fixed a 0.92/0.94 compatibility issue by writing two znodes in different formats.
> If a ZK failure occurs between the writing of the two znodes, strange behavior can result.
> This issue is a reminder to change these two ZK writes to use ZK.multi when we require ZK 3.4+. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira