You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org> on 2009/03/21 02:08:50 UTC

[jira] Updated: (HADOOP-5447) Logging turned on by default while using distcp

     [ https://issues.apache.org/jira/browse/HADOOP-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz Wo (Nicholas), SZE updated HADOOP-5447:
-------------------------------------------

    Issue Type: New Feature  (was: Bug)

For disable logging, you may change the values set in log4j.properties.

> 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.