[
https://issues.apache.org/jira/browse/HADOOP-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576443#comment-15576443
]
Andrew Wang commented on HADOOP-13717:
--------------------------------------
Man, the balancer is a can of worms. Not a daemon, but runs awkwardly longer
than other normal commands. This is the root of potential differences in
expectations.
What do you propose we do? Minimally, we should make sure all the members of
the balancer family have the same daemonization behavior, which is currently
untrue.
If part of the answer is that the balancer family are daemons and need a
HADOOP_LOG_DIR and a log4j.properties, that's fine with me. Not a hard change
on our side.
> Shell scripts call hadoop_verify_logdir even when command is not started as
> daemon
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-13717
> URL: https://issues.apache.org/jira/browse/HADOOP-13717
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
> Affects Versions: 3.0.0-alpha1
> Reporter: Andrew Wang
>
> Issue found when working with the HDFS balancer.
> In {{hadoop_daemon_handler}}, it calls {{hadoop_verify_logdir}} even for the
> "default" case which calls {{hadoop_start_daemon}}. {{daemon_outfile}} which
> specifies the log location isn't even used here, since the command is being
> started in the foreground.
> I think we can push the {{hadoop_verify_logdir}} call down into
> {{hadoop_start_daemon_wrapper}} instead, which does use the outfile.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
