You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2014/11/18 21:15:34 UTC
[jira] [Commented] (BIGTOP-1060) hadoop-hdfs-zkfc should stop
before hadoop-hdfs-namenode
[ https://issues.apache.org/jira/browse/BIGTOP-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216718#comment-14216718 ]
Konstantin Boudnik commented on BIGTOP-1060:
--------------------------------------------
Can anyone with a knowledge on Hadoop HA to comment/review, please?
> hadoop-hdfs-zkfc should stop before hadoop-hdfs-namenode
> --------------------------------------------------------
>
> Key: BIGTOP-1060
> URL: https://issues.apache.org/jira/browse/BIGTOP-1060
> Project: Bigtop
> Issue Type: Improvement
> Components: Init scripts
> Reporter: Masatake Iwasaki
> Assignee: Masatake Iwasaki
> Priority: Minor
> Attachments: BIGTOP-1060-0.patch
>
>
> Stopping namenode before zkfc possibly causes unnecessary fencing action.
> Current priority of namenode and zkfc are the same as default.
> {noformat}
> CHKCONFIG=${CHKCONFIG:-"2345 85 15"}
> {noformat}
> Because the highest priority among HDFS dependent services is "2345 87 13" of HBase, I think setting zkfs' priority to "2345 86 14" is good.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)