[
https://issues.apache.org/jira/browse/HADOOP-6746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878495#action_12878495
]
Gokul commented on HADOOP-6746:
-------------------------------
i am not getting the point here.
Currently, everytime you restart the cluster the log is getting appended right??
{quote}
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.
{quote}
can you make it elaborate?
> 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
>
> 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.
