[
https://issues.apache.org/jira/browse/HADOOP-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878844#action_12878844
]
Travis Crawford commented on HADOOP-6746:
-----------------------------------------
This is my first contribution to Hadoop, so sorry for the noobie question. At
this point (per http://wiki.apache.org/hadoop/HowToContribute) I believe the
next step is submitting the patch -- however, I either don't have permissions
to do so, or I'm being dense and not seeing that in the Jira interface.
If this change looks good a nudge in the right direction would be appreciated.
> hadoop-daemon.sh does not append to log files
> ---------------------------------------------
>
> Key: HADOOP-6746
> URL: https://issues.apache.org/jira/browse/HADOOP-6746
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Travis Crawford
> Attachments: HADOOP-6746.patch
>
>
> Looking in hadoop-daemon.sh we see the start command redirects logs to the
> log file by creating a new file. It does not append to the log.
> nohup nice -n $HADOOP_NICENESS "$HADOOP_HOME"/bin/hadoop --config
> $HADOOP_CONF_DIR $command "$@" > "$log" 2>&1 < /dev/null &
> I believe output should be appended to the log file so logrotate copytruncate
> works. Currently a large log file cannot be truncated without restarting the
> running service, which causes issues in production environments.
> The improved line would be exactly the same, except use >> to open the log
> file in append mode.
> nohup nice -n $HADOOP_NICENESS "$HADOOP_HOME"/bin/hadoop --config
> $HADOOP_CONF_DIR $command "$@" >> "$log" 2>&1 < /dev/null &
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
