You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2012/12/17 21:40:13 UTC

[jira] [Commented] (HBASE-6775) Use ZK.multi when available for HBASE-6710 0.92/0.94 compatibility fix

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

Hadoop QA commented on HBASE-6775:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12561348/HBASE-6775-v2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 8 new or modified tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3574//console

This message is automatically generated.
                
> 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
>
>         Attachments: HBASE-6775-v2.patch
>
>
> 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