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 "Arun C Murthy (JIRA)" <ji...@apache.org> on 2007/09/25 23:33:51 UTC

[jira] Created: (HADOOP-1944) Maps which ran on trackers declared 'lost' are being marked as FAILED rather than KILLED

Maps which ran on trackers declared 'lost' are being marked as FAILED rather than KILLED
----------------------------------------------------------------------------------------

                 Key: HADOOP-1944
                 URL: https://issues.apache.org/jira/browse/HADOOP-1944
             Project: Hadoop
          Issue Type: Bug
          Components: mapred
    Affects Versions: 0.15.0
            Reporter: Arun C Murthy
            Assignee: Arun C Murthy
            Priority: Blocker
             Fix For: 0.15.0


There seems to be a bug in {{TaskInProgress.taskKilled}} which checks if that taskid was in {{tasksToKill}}, if not, it just marks the taskid as FAILED. This is wrong since tasks can also be KILLED due to *lost task-trackers* and hence won't be found in {{tasksToKill}}.

This clearly leads to a wrongly penalizing user-jobs.

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


[jira] Commented: (HADOOP-1944) Maps which ran on trackers declared 'lost' are being marked as FAILED rather than KILLED

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

Devaraj Das commented on HADOOP-1944:
-------------------------------------

This will be addressed by the patch for HADOOP-1874. 

> Maps which ran on trackers declared 'lost' are being marked as FAILED rather than KILLED
> ----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1944
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1944
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.15.0
>            Reporter: Arun C Murthy
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.15.0
>
>
> There seems to be a bug in {{TaskInProgress.taskKilled}} which checks if that taskid was in {{tasksToKill}}, if not, it just marks the taskid as FAILED. This is wrong since tasks can also be KILLED due to *lost task-trackers* and hence won't be found in {{tasksToKill}}.
> This clearly leads to a wrongly penalizing user-jobs.

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


[jira] Resolved: (HADOOP-1944) Maps which ran on trackers declared 'lost' are being marked as FAILED rather than KILLED

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

Devaraj Das resolved HADOOP-1944.
---------------------------------

    Resolution: Fixed

Since HADOOP-1874 addresses the bug in this issue, I am closing it.

> Maps which ran on trackers declared 'lost' are being marked as FAILED rather than KILLED
> ----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1944
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1944
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.15.0
>            Reporter: Arun C Murthy
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.15.0
>
>
> There seems to be a bug in {{TaskInProgress.taskKilled}} which checks if that taskid was in {{tasksToKill}}, if not, it just marks the taskid as FAILED. This is wrong since tasks can also be KILLED due to *lost task-trackers* and hence won't be found in {{tasksToKill}}.
> This clearly leads to a wrongly penalizing user-jobs.

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


[jira] Assigned: (HADOOP-1944) Maps which ran on trackers declared 'lost' are being marked as FAILED rather than KILLED

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

Devaraj Das reassigned HADOOP-1944:
-----------------------------------

    Assignee: Devaraj Das  (was: Arun C Murthy)

> Maps which ran on trackers declared 'lost' are being marked as FAILED rather than KILLED
> ----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1944
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1944
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.15.0
>            Reporter: Arun C Murthy
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.15.0
>
>
> There seems to be a bug in {{TaskInProgress.taskKilled}} which checks if that taskid was in {{tasksToKill}}, if not, it just marks the taskid as FAILED. This is wrong since tasks can also be KILLED due to *lost task-trackers* and hence won't be found in {{tasksToKill}}.
> This clearly leads to a wrongly penalizing user-jobs.

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