[ 
https://issues.apache.org/jira/browse/HDFS-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suresh Srinivas updated HDFS-1974:
----------------------------------

    Attachment: HDFS-1974.6.patch

New patch that addresses the comments from Aaron. Here is the test-patch result:
     [exec] -1 overall.  
     [exec] 
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec] 
     [exec]     -1 tests included.  The patch doesn't appear to include any new 
or modified tests.
     [exec]                         Please justify why no new tests are needed 
for this patch.
     [exec]                         Also please list what manual steps were 
performed to verify this patch.
     [exec] 
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning 
messages.
     [exec] 
     [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
     [exec] 
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs 
(version 1.3.9) warnings.
     [exec] 
     [exec]     -1 release audit.  The applied patch generated 1 release audit 
warnings (more than the trunk's current 0 warnings).
     [exec] 
     [exec]     +1 system test framework.  The patch passed system test 
framework compile.
     [exec] 


Release audit comes from missing banner in CHANGES.HDFS-1623.txt. Will fix that 
in a different commit.

> HA: Introduce active and standby states to the namenode
> -------------------------------------------------------
>
>                 Key: HDFS-1974
>                 URL: https://issues.apache.org/jira/browse/HDFS-1974
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: HDFS-1974.1.patch, HDFS-1974.2.patch, HDFS-1974.3.patch, 
> HDFS-1974.4.patch, HDFS-1974.5.patch, HDFS-1974.6.patch, HDFS-1974.patch
>
>
> Currently namenode supports active, secondary and backup roles. To support 
> namenode high availability, active and standby states are needed. Note that 
> this is different from the existing notion of namenode role, where a namenode 
> cannot transition from one role to the other.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to