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 "Chris Douglas (JIRA)" <ji...@apache.org> on 2007/10/11 01:20:50 UTC

[jira] Created: (HADOOP-2028) distcp fails if log dir not specified and destination not present

distcp fails if log dir not specified and destination not present
-----------------------------------------------------------------

                 Key: HADOOP-2028
                 URL: https://issues.apache.org/jira/browse/HADOOP-2028
             Project: Hadoop
          Issue Type: Bug
          Components: util
            Reporter: Chris Douglas
            Priority: Blocker
             Fix For: 0.15.0


The default location for distcp logs is in the destination directory; when that doesn't exist, distcp exits with an error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-2028) distcp fails if log dir not specified and destination not present

Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534095 ] 

Chris Douglas commented on HADOOP-2028:
---------------------------------------

The hbase test that failed is not related to this patch.

> distcp fails if log dir not specified and destination not present
> -----------------------------------------------------------------
>
>                 Key: HADOOP-2028
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2028
>             Project: Hadoop
>          Issue Type: Bug
>          Components: util
>            Reporter: Chris Douglas
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: 2028.patch
>
>
> The default location for distcp logs is in the destination directory; when that doesn't exist, distcp exits with an error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-2028) distcp fails if log dir not specified and destination not present

Posted by "Runping Qi (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533904 ] 

Runping Qi commented on HADOOP-2028:
------------------------------------

the job fails too if the specified log dir is not empty


> distcp fails if log dir not specified and destination not present
> -----------------------------------------------------------------
>
>                 Key: HADOOP-2028
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2028
>             Project: Hadoop
>          Issue Type: Bug
>          Components: util
>            Reporter: Chris Douglas
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: 2028.patch
>
>
> The default location for distcp logs is in the destination directory; when that doesn't exist, distcp exits with an error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-2028) distcp fails if log dir not specified and destination not present

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534043 ] 

Hadoop QA commented on HADOOP-2028:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12367537/2028.patch
against trunk revision r583424.

    @author +1.  The patch does not contain any @author tags.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests -1.  The patch failed contrib unit tests.

Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/923/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/923/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/923/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/923/console

This message is automatically generated.

> distcp fails if log dir not specified and destination not present
> -----------------------------------------------------------------
>
>                 Key: HADOOP-2028
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2028
>             Project: Hadoop
>          Issue Type: Bug
>          Components: util
>            Reporter: Chris Douglas
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: 2028.patch
>
>
> The default location for distcp logs is in the destination directory; when that doesn't exist, distcp exits with an error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-2028) distcp fails if log dir not specified and destination not present

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534523 ] 

Hudson commented on HADOOP-2028:
--------------------------------

Integrated in Hadoop-Nightly #270 (See [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/270/])

> distcp fails if log dir not specified and destination not present
> -----------------------------------------------------------------
>
>                 Key: HADOOP-2028
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2028
>             Project: Hadoop
>          Issue Type: Bug
>          Components: util
>            Reporter: Chris Douglas
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: 2028.patch
>
>
> The default location for distcp logs is in the destination directory; when that doesn't exist, distcp exits with an error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-2028) distcp fails if log dir not specified and destination not present

Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Douglas updated HADOOP-2028:
----------------------------------

    Attachment: 2028.patch

This fixes the default log behavior. It also logs when files are skipped, instead of simply setting the reporter status (which is almost immediately lost).

> distcp fails if log dir not specified and destination not present
> -----------------------------------------------------------------
>
>                 Key: HADOOP-2028
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2028
>             Project: Hadoop
>          Issue Type: Bug
>          Components: util
>            Reporter: Chris Douglas
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: 2028.patch
>
>
> The default location for distcp logs is in the destination directory; when that doesn't exist, distcp exits with an error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-2028) distcp fails if log dir not specified and destination not present

Posted by "Nigel Daley (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nigel Daley updated HADOOP-2028:
--------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I just committed this.  Thanks Chris!

> distcp fails if log dir not specified and destination not present
> -----------------------------------------------------------------
>
>                 Key: HADOOP-2028
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2028
>             Project: Hadoop
>          Issue Type: Bug
>          Components: util
>            Reporter: Chris Douglas
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: 2028.patch
>
>
> The default location for distcp logs is in the destination directory; when that doesn't exist, distcp exits with an error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-2028) distcp fails if log dir not specified and destination not present

Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533931 ] 

Chris Douglas commented on HADOOP-2028:
---------------------------------------

Since it doesn't do a reduce, distcp uses mapred.output.dir for its "logs". Would it be reasonable to generate and use a random subdirectory in the user-specified log directory?

> distcp fails if log dir not specified and destination not present
> -----------------------------------------------------------------
>
>                 Key: HADOOP-2028
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2028
>             Project: Hadoop
>          Issue Type: Bug
>          Components: util
>            Reporter: Chris Douglas
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: 2028.patch
>
>
> The default location for distcp logs is in the destination directory; when that doesn't exist, distcp exits with an error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-2028) distcp fails if log dir not specified and destination not present

Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534403 ] 

Owen O'Malley commented on HADOOP-2028:
---------------------------------------

+1

> distcp fails if log dir not specified and destination not present
> -----------------------------------------------------------------
>
>                 Key: HADOOP-2028
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2028
>             Project: Hadoop
>          Issue Type: Bug
>          Components: util
>            Reporter: Chris Douglas
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: 2028.patch
>
>
> The default location for distcp logs is in the destination directory; when that doesn't exist, distcp exits with an error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-2028) distcp fails if log dir not specified and destination not present

Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Douglas updated HADOOP-2028:
----------------------------------

    Status: Patch Available  (was: Open)

> distcp fails if log dir not specified and destination not present
> -----------------------------------------------------------------
>
>                 Key: HADOOP-2028
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2028
>             Project: Hadoop
>          Issue Type: Bug
>          Components: util
>            Reporter: Chris Douglas
>            Priority: Blocker
>             Fix For: 0.15.0
>
>         Attachments: 2028.patch
>
>
> The default location for distcp logs is in the destination directory; when that doesn't exist, distcp exits with an error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.