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 "Devaraj Das (JIRA)" <ji...@apache.org> on 2008/04/18 19:04:23 UTC

[jira] Created: (HADOOP-3279) TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
----------------------------------------------------------------------------------------------------------------------------------

                 Key: HADOOP-3279
                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
             Project: Hadoop Core
          Issue Type: Bug
          Components: mapred
    Affects Versions: 0.17.0
            Reporter: Devaraj Das
            Assignee: Devaraj Das
            Priority: Blocker
             Fix For: 0.17.0
         Attachments: 3279.patch

Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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


[jira] Updated: (HADOOP-3279) TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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

Devaraj Das updated HADOOP-3279:
--------------------------------

    Attachment: 3279.patch

> TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: 3279.patch, 3279.patch
>
>
> Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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


[jira] Resolved: (HADOOP-3279) TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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

Devaraj Das resolved HADOOP-3279.
---------------------------------

    Resolution: Fixed

I just committed this.

> TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: 3279.patch, 3279.patch
>
>
> Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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


[jira] Updated: (HADOOP-3279) TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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

Devaraj Das updated HADOOP-3279:
--------------------------------

    Status: Patch Available  (was: Open)

> TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: 3279.patch
>
>
> Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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


[jira] Commented: (HADOOP-3279) TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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

Hudson commented on HADOOP-3279:
--------------------------------

Integrated in Hadoop-trunk #467 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/467/])

> TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: 3279.patch, 3279.patch
>
>
> Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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


[jira] Updated: (HADOOP-3279) TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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

Devaraj Das updated HADOOP-3279:
--------------------------------

    Status: Patch Available  (was: Open)

> TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: 3279.patch, 3279.patch
>
>
> Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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


[jira] Reopened: (HADOOP-3279) TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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

Devaraj Das reopened HADOOP-3279:
---------------------------------


> TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: 3279.patch, 3279.patch
>
>
> Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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


[jira] Updated: (HADOOP-3279) TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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

Devaraj Das updated HADOOP-3279:
--------------------------------

    Status: Open  (was: Patch Available)

Attached the wrong file. Cancelling the patch..

> TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: 3279.patch, 3279.patch
>
>
> Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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


[jira] Commented: (HADOOP-3279) TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590525#action_12590525 ] 

Arun C Murthy commented on HADOOP-3279:
---------------------------------------

+1

> TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: 3279.patch, 3279.patch
>
>
> Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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


[jira] Commented: (HADOOP-3279) TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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

Hadoop QA commented on HADOOP-3279:
-----------------------------------

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

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

    tests included -1.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no tests are needed for this patch.

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

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

    release audit +1.  The applied patch does not generate any new release audit 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 passed contrib unit tests.

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

This message is automatically generated.

> TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: 3279.patch, 3279.patch
>
>
> Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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


[jira] Updated: (HADOOP-3279) TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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

Devaraj Das updated HADOOP-3279:
--------------------------------

    Comment: was deleted

> TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: 3279.patch, 3279.patch
>
>
> Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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


[jira] Updated: (HADOOP-3279) TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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

Devaraj Das updated HADOOP-3279:
--------------------------------

    Attachment: 3279.patch

Straightforward patch..

> TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: 3279.patch
>
>
> Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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


[jira] Updated: (HADOOP-3279) TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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

Amar Kamat updated HADOOP-3279:
-------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

I just committed this.

> TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3279
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.17.0
>
>         Attachments: 3279.patch, 3279.patch
>
>
> Post HADOOP-3140, tasks could be marked as SUCCEEDED by the TaskTracker. Hence, the TaskTracker should check for SUCCEEDED task status in addition to COMMIT_PENDING status when it fails maps due to lost map outputs

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