[
https://issues.apache.org/jira/browse/HDFS-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205420#comment-13205420
]
Hudson commented on HDFS-2912:
------------------------------
Integrated in Hadoop-Hdfs-HAbranch-build #74 (See
[https://builds.apache.org/job/Hadoop-Hdfs-HAbranch-build/74/])
HDFS-2912. Namenode not shutting down when shared edits dir is
inaccessible. Contributed by Bikas Saha.
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1242564
Files :
*
/hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/CHANGES.HDFS-1623.txt
*
/hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLog.java
*
/hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/JournalSet.java
*
/hadoop/common/branches/HDFS-1623/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestFailureOfSharedDir.java
> HA: Namenode not shutting down when shared edits dir is inaccessible
> --------------------------------------------------------------------
>
> Key: HDFS-2912
> URL: https://issues.apache.org/jira/browse/HDFS-2912
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Fix For: HA branch (HDFS-1623)
>
> Attachments: HDFS-2909.HDFS-1623.patch, HDFS-2912.HDFS-1623.patch,
> HDFS-2912.HDFS-1623.patch
>
>
> When there is an error in shared edits dir then current policy requires the
> active name node to abort and shutdown.
> Currently there is no way to shut down the name node and hence this does not
> happen even after all journals have been aborted on error. In fact the name
> node stays Active and also is not in safe mode. Ideally it should shut down,
> or at least go into safe mode or standby mode.
--
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
