[
https://issues.apache.org/jira/browse/HADOOP-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700318#action_12700318
]
Tsz Wo (Nicholas), SZE commented on HADOOP-5447:
------------------------------------------------
> For disable logging, you may change the values set in log4j.properties.
Oops, I mis-understood the problem.
In such case, you may use -log <logdir> to specify a logging directory, say
/tmp/foo, which is outside the critical applications' directories. Of course,
it is still good to have the suggested new feature.
> Logging turned on by default while using distcp
> -----------------------------------------------
>
> Key: HADOOP-5447
> URL: https://issues.apache.org/jira/browse/HADOOP-5447
> Project: Hadoop Core
> Issue Type: New Feature
> Components: tools/distcp
> Affects Versions: 0.18.2, 0.18.3
> Environment: Linux RHEL54, Linux RHEL5
> Reporter: Sanjeev Jaiswal
> Fix For: 0.20.0, 0.21.0
>
>
> Distcp should have an option to disable logging during a distcp
> eg: hadoop distcp --nolog <source dir> <destination dir>
> By default logging is enabled or turned on while using distcp.This generates
> logs in DFS, which need to be cleaned up periodically. During this time,
> critical applications sometimes fail, when they see distcp logs in the DFS.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
