[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871018#action_12871018
 ] 

Hadoop QA commented on ZOOKEEPER-779:
-------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12445423/ZOOKEEPER-779.patch
  against trunk revision 947063.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified 
tests.
                        Please justify why no tests are needed for this patch.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    -1 core tests.  The patch failed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/105/testReport/
Findbugs warnings: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/105/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/105/console

This message is automatically generated.

> C Client should check the connectivity to the hosts in zookeeper_init
> ---------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-779
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-779
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: c client
>    Affects Versions: 3.3.1
>            Reporter: Qian Ye
>         Attachments: ZOOKEEPER-779.patch, ZOOKEEPER-779.patch
>
>
> In some scenario, whether the client can connect to zookeeper servers is used 
> as a logic condition. If the client cannot connect to the servers, the 
> program should turn to another fork. However, current zookeeper_init could 
> not tell whether the client can connect to one server or not. It could make 
> some users feel confused. I think we should check the connectivity to the 
> host in zookeeper_init, so we can tell whether the hosts are avaiable at that 
> time or not.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to