[
https://issues.apache.org/jira/browse/HDFS-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14387349#comment-14387349
]
Jing Zhao commented on HDFS-8003:
---------------------------------
Thanks for the comments, [~aw]. The description of HDFS-6353 states the main
motivation scenario:
bq. One of the failure patterns I have seen is, in some rare circumstances, due
to some inconsistency the secondary or standby fails to consume editlog. The
only solution when this happens is to save the namespace at the current active
namenode. But sometimes when this happens, unsuspecting admin might end up
restarting the namenode, requiring more complicated solution to the problem
(such as ignore editlog record that cannot be consumed etc.).
Thus the feature aims to prevent users from stopping namenode while the
standby/secondary NN failed to checkpoint due to corruption. With new changes
in HDFS-7991, if the feature is on, the shell code will exit if the checkpoint
fails and the NN will not be stopped.
> hdfs has 3 new shellcheck warnings and the related code change is questionable
> ------------------------------------------------------------------------------
>
> Key: HDFS-8003
> URL: https://issues.apache.org/jira/browse/HDFS-8003
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
>
> HDFS-6353 introduced three new shell check warnings due to an unprotected
> ${HADOOP_OPTS}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
