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 "Owen O'Malley (JIRA)" <ji...@apache.org> on 2007/08/21 22:08:31 UTC

[jira] Created: (HADOOP-1748) Task Trackers fail to launch tasks when they have relative log directories configured

Task Trackers fail to launch tasks when they have relative log directories configured
-------------------------------------------------------------------------------------

                 Key: HADOOP-1748
                 URL: https://issues.apache.org/jira/browse/HADOOP-1748
             Project: Hadoop
          Issue Type: Bug
          Components: mapred
    Affects Versions: 0.14.0
            Reporter: Owen O'Malley
            Assignee: Owen O'Malley
             Fix For: 0.15.0


Task Trackers use the configured log directory to get the locations of the user log files. The Task Tracker does a mkdir, but the task is in a different current directory. Therefore, the directory does not exist and the Task fails.

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


[jira] Updated: (HADOOP-1748) Task Trackers fail to launch tasks when they have relative log directories configured

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

Owen O'Malley updated HADOOP-1748:
----------------------------------

    Attachment: relative-path-logdir.patch

This patch makes the log directory absolute, so that they don't change in the child jvm.

> Task Trackers fail to launch tasks when they have relative log directories configured
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1748
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1748
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.15.0
>
>         Attachments: relative-path-logdir.patch
>
>
> Task Trackers use the configured log directory to get the locations of the user log files. The Task Tracker does a mkdir, but the task is in a different current directory. Therefore, the directory does not exist and the Task fails.

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


[jira] Commented: (HADOOP-1748) Task Trackers fail to launch tasks when they have relative log directories configured

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

Hadoop QA commented on HADOOP-1748:
-----------------------------------

+1

http://issues.apache.org/jira/secure/attachment/12364261/relative-path-logdir.patch applied and successfully tested against trunk revision r569501.

Test results:   http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/616/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/616/console

> Task Trackers fail to launch tasks when they have relative log directories configured
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1748
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1748
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.15.0
>
>         Attachments: relative-path-logdir.patch
>
>
> Task Trackers use the configured log directory to get the locations of the user log files. The Task Tracker does a mkdir, but the task is in a different current directory. Therefore, the directory does not exist and the Task fails.

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


[jira] Commented: (HADOOP-1748) Task Trackers fail to launch tasks when they have relative log directories configured

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

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

I thought it was better to do that as another patch, HADOOP-1750.

> Task Trackers fail to launch tasks when they have relative log directories configured
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1748
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1748
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.15.0
>
>         Attachments: relative-path-logdir.patch
>
>
> Task Trackers use the configured log directory to get the locations of the user log files. The Task Tracker does a mkdir, but the task is in a different current directory. Therefore, the directory does not exist and the Task fails.

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


[jira] Updated: (HADOOP-1748) Task Trackers fail to launch tasks when they have relative log directories configured

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

Doug Cutting updated HADOOP-1748:
---------------------------------

    Status: Patch Available  (was: Open)

> Task Trackers fail to launch tasks when they have relative log directories configured
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1748
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1748
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.15.0
>
>         Attachments: relative-path-logdir.patch
>
>
> Task Trackers use the configured log directory to get the locations of the user log files. The Task Tracker does a mkdir, but the task is in a different current directory. Therefore, the directory does not exist and the Task fails.

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


[jira] Updated: (HADOOP-1748) Task Trackers fail to launch tasks when they have relative log directories configured

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

Doug Cutting updated HADOOP-1748:
---------------------------------

    Status: Open  (was: Patch Available)

The build failure seemed unrelated to this patch.

> Task Trackers fail to launch tasks when they have relative log directories configured
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1748
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1748
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.15.0
>
>         Attachments: relative-path-logdir.patch
>
>
> Task Trackers use the configured log directory to get the locations of the user log files. The Task Tracker does a mkdir, but the task is in a different current directory. Therefore, the directory does not exist and the Task fails.

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


[jira] Commented: (HADOOP-1748) Task Trackers fail to launch tasks when they have relative log directories configured

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

Hadoop QA commented on HADOOP-1748:
-----------------------------------

-1, build or testing failed

2 attempts failed to build and test the latest attachment http://issues.apache.org/jira/secure/attachment/12364261/relative-path-logdir.patch against trunk revision r568303.

Test results:   http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/588/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/588/console

Please note that this message is automatically generated and may represent a problem with the automation system and not the patch.

> Task Trackers fail to launch tasks when they have relative log directories configured
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1748
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1748
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.15.0
>
>         Attachments: relative-path-logdir.patch
>
>
> Task Trackers use the configured log directory to get the locations of the user log files. The Task Tracker does a mkdir, but the task is in a different current directory. Therefore, the directory does not exist and the Task fails.

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


[jira] Updated: (HADOOP-1748) Task Trackers fail to launch tasks when they have relative log directories configured

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

Owen O'Malley updated HADOOP-1748:
----------------------------------

    Status: Patch Available  (was: Open)

> Task Trackers fail to launch tasks when they have relative log directories configured
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1748
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1748
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.15.0
>
>         Attachments: relative-path-logdir.patch
>
>
> Task Trackers use the configured log directory to get the locations of the user log files. The Task Tracker does a mkdir, but the task is in a different current directory. Therefore, the directory does not exist and the Task fails.

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


[jira] Commented: (HADOOP-1748) Task Trackers fail to launch tasks when they have relative log directories configured

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

Konstantin Shvachko commented on HADOOP-1748:
---------------------------------------------

It would also be good to improve logging messages.
Printing the status of a failed task does not say a lot about why it failed. 
The real error message could have saved us a lot of time.

> Task Trackers fail to launch tasks when they have relative log directories configured
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1748
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1748
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.15.0
>
>         Attachments: relative-path-logdir.patch
>
>
> Task Trackers use the configured log directory to get the locations of the user log files. The Task Tracker does a mkdir, but the task is in a different current directory. Therefore, the directory does not exist and the Task fails.

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


[jira] Updated: (HADOOP-1748) Task Trackers fail to launch tasks when they have relative log directories configured

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

Doug Cutting updated HADOOP-1748:
---------------------------------

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

I just committed this.  Thanks, Owen!

> Task Trackers fail to launch tasks when they have relative log directories configured
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1748
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1748
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.0
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.15.0
>
>         Attachments: relative-path-logdir.patch
>
>
> Task Trackers use the configured log directory to get the locations of the user log files. The Task Tracker does a mkdir, but the task is in a different current directory. Therefore, the directory does not exist and the Task fails.

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