[
https://issues.apache.org/jira/browse/HDFS-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474057#comment-13474057
]
Hadoop QA commented on HDFS-3562:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12548715/HDFS-3562.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 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs/src/contrib/bkjournal.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/3313//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3313//console
This message is automatically generated.
> Handle disconnect and session timeout events at BKJM
> ----------------------------------------------------
>
> Key: HDFS-3562
> URL: https://issues.apache.org/jira/browse/HDFS-3562
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Vinay
> Assignee: Vinay
> Attachments: HDFS-3562.patch, HDFS-3562.patch
>
>
> # Retry zookeeper operations for some amount of time in case of
> CONNECTIONLOSS/OPERATIONTIMEOUT exceptions.
> # In case of Session expiry trigger shutdown
--
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
