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

Hadoop QA commented on HDFS-3211:
---------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12521730/HDFS-3211.txt
  against trunk revision .

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

    +1 tests included.  The patch appears to include 1 new or modified test 
files.

    +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 eclipse:eclipse.  The patch built with eclipse:eclipse.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) 
warnings.

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

    +1 core tests.  The patch passed unit tests in .

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

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/2217//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2217//console

This message is automatically generated.
                
> JournalProtocol changes required for introducing epoch and fencing
> ------------------------------------------------------------------
>
>                 Key: HDFS-3211
>                 URL: https://issues.apache.org/jira/browse/HDFS-3211
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha, name-node
>    Affects Versions: Shared journals (HDFS-3092)
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: HDFS-3211.txt, HDFS-3211.txt, HDFS-3211.txt, 
> HDFS-3211.txt, HDFS-3211.txt
>
>
> JournalProtocol changes to introduce epoch in every request. Adding new 
> method fence for fencing a JournalService. On BackupNode fence is a no-op. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to