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

Hudson commented on HDFS-15223:
-------------------------------

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #18067 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/18067/])
HDFS-15223. FSCK fails if one namenode is not available. Contributed by 
(ayushsaxena: rev bb41ddaf1e0c9bf44830b2cf0ac653b7354abf46)
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestHAFsck.java
* (edit) 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HAUtil.java


> FSCK fails if one namenode is not available
> -------------------------------------------
>
>                 Key: HDFS-15223
>                 URL: https://issues.apache.org/jira/browse/HDFS-15223
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Ayush Saxena
>            Assignee: Ayush Saxena
>            Priority: Major
>             Fix For: 3.3.0
>
>         Attachments: HDFS-15223-01.patch, HDFS-15223-02.patch
>
>
> If one namenode is not available FSCK should try on other namenode, ignoring 
> the namenode not available



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to