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 "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2007/12/07 12:39:43 UTC

[jira] Created: (HADOOP-2378) last TaskCompletionEvent gets added to the job after the job is marked as completed

last TaskCompletionEvent gets added to the job after the job is marked as completed
-----------------------------------------------------------------------------------

                 Key: HADOOP-2378
                 URL: https://issues.apache.org/jira/browse/HADOOP-2378
             Project: Hadoop
          Issue Type: Bug
          Components: mapred
         Environment: all
            Reporter: Alejandro Abdelnur
            Priority: Blocker
             Fix For: 0.15.2


In the JobInProgress the last TaskCompletionEvent gets added to the job after the completedTask() method is invoked.

The completedTask() method has to be invoked after the completion event is added to the job.

If not when the job is moved into completed before the last completion event is in the job causing a temporary inconsistency in the JT as one task completion event is still missing.

This blocks a fix for HADOOP-1876 where the job info is persisted as soon as the job is completed, thus the last completion event is missing.



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


[jira] Updated: (HADOOP-2378) last TaskCompletionEvent gets added to the job after the job is marked as completed

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

Alejandro Abdelnur updated HADOOP-2378:
---------------------------------------

    Attachment: patch2378.txt

adding comments on why the change is safe

> last TaskCompletionEvent gets added to the job after the job is marked as completed
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-2378
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2378
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Priority: Blocker
>             Fix For: 0.15.2
>
>         Attachments: patch2378.txt, patch2378.txt
>
>
> In the JobInProgress the last TaskCompletionEvent gets added to the job after the completedTask() method is invoked.
> The completedTask() method has to be invoked after the completion event is added to the job.
> If not when the job is moved into completed before the last completion event is in the job causing a temporary inconsistency in the JT as one task completion event is still missing.
> This blocks a fix for HADOOP-1876 where the job info is persisted as soon as the job is completed, thus the last completion event is missing.

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


[jira] Commented: (HADOOP-2378) last TaskCompletionEvent gets added to the job after the job is marked as completed

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

Hadoop QA commented on HADOOP-2378:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12371506/patch2378.txt
against trunk revision r603428.

    @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 passed contrib unit tests.

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

This message is automatically generated.

> last TaskCompletionEvent gets added to the job after the job is marked as completed
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-2378
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2378
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Priority: Blocker
>             Fix For: 0.15.2
>
>         Attachments: patch2378.txt, patch2378.txt
>
>
> In the JobInProgress the last TaskCompletionEvent gets added to the job after the completedTask() method is invoked.
> The completedTask() method has to be invoked after the completion event is added to the job.
> If not when the job is moved into completed before the last completion event is in the job causing a temporary inconsistency in the JT as one task completion event is still missing.
> This blocks a fix for HADOOP-1876 where the job info is persisted as soon as the job is completed, thus the last completion event is missing.

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


[jira] Updated: (HADOOP-2378) last TaskCompletionEvent gets added to the job after the job is marked as completed

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

Alejandro Abdelnur updated HADOOP-2378:
---------------------------------------

    Attachment: patch2378.txt

> last TaskCompletionEvent gets added to the job after the job is marked as completed
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-2378
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2378
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Priority: Blocker
>             Fix For: 0.15.2
>
>         Attachments: patch2378.txt
>
>
> In the JobInProgress the last TaskCompletionEvent gets added to the job after the completedTask() method is invoked.
> The completedTask() method has to be invoked after the completion event is added to the job.
> If not when the job is moved into completed before the last completion event is in the job causing a temporary inconsistency in the JT as one task completion event is still missing.
> This blocks a fix for HADOOP-1876 where the job info is persisted as soon as the job is completed, thus the last completion event is missing.

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


[jira] Updated: (HADOOP-2378) last TaskCompletionEvent gets added to the job after the job is marked as completed

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

Devaraj Das updated HADOOP-2378:
--------------------------------

    Resolution: Fixed
      Assignee: Devaraj Das
        Status: Resolved  (was: Patch Available)

I just committed this. Thanks, Alejandro!

> last TaskCompletionEvent gets added to the job after the job is marked as completed
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-2378
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2378
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.15.2
>
>         Attachments: patch2378.txt, patch2378.txt
>
>
> In the JobInProgress the last TaskCompletionEvent gets added to the job after the completedTask() method is invoked.
> The completedTask() method has to be invoked after the completion event is added to the job.
> If not when the job is moved into completed before the last completion event is in the job causing a temporary inconsistency in the JT as one task completion event is still missing.
> This blocks a fix for HADOOP-1876 where the job info is persisted as soon as the job is completed, thus the last completion event is missing.

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


[jira] Commented: (HADOOP-2378) last TaskCompletionEvent gets added to the job after the job is marked as completed

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

Hudson commented on HADOOP-2378:
--------------------------------

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

> last TaskCompletionEvent gets added to the job after the job is marked as completed
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-2378
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2378
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.15.2
>
>         Attachments: patch2378.txt, patch2378.txt
>
>
> In the JobInProgress the last TaskCompletionEvent gets added to the job after the completedTask() method is invoked.
> The completedTask() method has to be invoked after the completion event is added to the job.
> If not when the job is moved into completed before the last completion event is in the job causing a temporary inconsistency in the JT as one task completion event is still missing.
> This blocks a fix for HADOOP-1876 where the job info is persisted as soon as the job is completed, thus the last completion event is missing.

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


[jira] Updated: (HADOOP-2378) last TaskCompletionEvent gets added to the job after the job is marked as completed

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

Alejandro Abdelnur updated HADOOP-2378:
---------------------------------------

    Status: Patch Available  (was: Open)

> last TaskCompletionEvent gets added to the job after the job is marked as completed
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-2378
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2378
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Priority: Blocker
>             Fix For: 0.15.2
>
>         Attachments: patch2378.txt
>
>
> In the JobInProgress the last TaskCompletionEvent gets added to the job after the completedTask() method is invoked.
> The completedTask() method has to be invoked after the completion event is added to the job.
> If not when the job is moved into completed before the last completion event is in the job causing a temporary inconsistency in the JT as one task completion event is still missing.
> This blocks a fix for HADOOP-1876 where the job info is persisted as soon as the job is completed, thus the last completion event is missing.

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


[jira] Commented: (HADOOP-2378) last TaskCompletionEvent gets added to the job after the job is marked as completed

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

Hadoop QA commented on HADOOP-2378:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12371221/patch2378.txt
against trunk revision r602002.

    @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 passed contrib unit tests.

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

This message is automatically generated.

> last TaskCompletionEvent gets added to the job after the job is marked as completed
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-2378
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2378
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Priority: Blocker
>             Fix For: 0.15.2
>
>         Attachments: patch2378.txt
>
>
> In the JobInProgress the last TaskCompletionEvent gets added to the job after the completedTask() method is invoked.
> The completedTask() method has to be invoked after the completion event is added to the job.
> If not when the job is moved into completed before the last completion event is in the job causing a temporary inconsistency in the JT as one task completion event is still missing.
> This blocks a fix for HADOOP-1876 where the job info is persisted as soon as the job is completed, thus the last completion event is missing.

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


[jira] Updated: (HADOOP-2378) last TaskCompletionEvent gets added to the job after the job is marked as completed

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

Alejandro Abdelnur updated HADOOP-2378:
---------------------------------------

    Status: Open  (was: Patch Available)

> last TaskCompletionEvent gets added to the job after the job is marked as completed
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-2378
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2378
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Priority: Blocker
>             Fix For: 0.15.2
>
>         Attachments: patch2378.txt, patch2378.txt
>
>
> In the JobInProgress the last TaskCompletionEvent gets added to the job after the completedTask() method is invoked.
> The completedTask() method has to be invoked after the completion event is added to the job.
> If not when the job is moved into completed before the last completion event is in the job causing a temporary inconsistency in the JT as one task completion event is still missing.
> This blocks a fix for HADOOP-1876 where the job info is persisted as soon as the job is completed, thus the last completion event is missing.

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


[jira] Updated: (HADOOP-2378) last TaskCompletionEvent gets added to the job after the job is marked as completed

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

Alejandro Abdelnur updated HADOOP-2378:
---------------------------------------

    Status: Patch Available  (was: Open)

> last TaskCompletionEvent gets added to the job after the job is marked as completed
> -----------------------------------------------------------------------------------
>
>                 Key: HADOOP-2378
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2378
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Priority: Blocker
>             Fix For: 0.15.2
>
>         Attachments: patch2378.txt, patch2378.txt
>
>
> In the JobInProgress the last TaskCompletionEvent gets added to the job after the completedTask() method is invoked.
> The completedTask() method has to be invoked after the completion event is added to the job.
> If not when the job is moved into completed before the last completion event is in the job causing a temporary inconsistency in the JT as one task completion event is still missing.
> This blocks a fix for HADOOP-1876 where the job info is persisted as soon as the job is completed, thus the last completion event is missing.

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