You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Olga Natkovich (JIRA)" <ji...@apache.org> on 2008/10/08 01:44:44 UTC

[jira] Created: (PIG-475) "task failed to report status" error

"task failed to report status" error
------------------------------------

                 Key: PIG-475
                 URL: https://issues.apache.org/jira/browse/PIG-475
             Project: Pig
          Issue Type: Bug
    Affects Versions: types_branch
            Reporter: Olga Natkovich
            Assignee: Shravan Matthur Narayanamurthy
             Fix For: types_branch


When running a very large query a user got the following error after 90 minutes:

org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.Launcher
>> - Error message from task (reduce) tip_200810072143_0004_r_000033Task
>> task_200810072143_0004_r_000033_0 failed to report status for 600 
>> seconds. Killing!

Looks like we missed reporting progress in a few places.

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


[jira] Issue Comment Edited: (PIG-475) "task failed to report status" error

Posted by "Shravan Matthur Narayanamurthy (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PIG-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638665#action_12638665 ] 

shravanmn edited comment on PIG-475 at 10/10/08 3:34 PM:
------------------------------------------------------------------------------

The PhysicalOperator.reporter initialization in PigMapReduce.Reduce.reduce was missing

      was (Author: shravanmn):
    Had missed initializing the PhysicalOperator.reporter in PigMapReduce.Reduce.reduce
  
> "task failed to report status" error
> ------------------------------------
>
>                 Key: PIG-475
>                 URL: https://issues.apache.org/jira/browse/PIG-475
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: types_branch
>            Reporter: Olga Natkovich
>            Assignee: Shravan Matthur Narayanamurthy
>             Fix For: types_branch
>
>         Attachments: 475.patch
>
>
> When running a very large query a user got the following error after 90 minutes:
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.Launcher
> >> - Error message from task (reduce) tip_200810072143_0004_r_000033Task
> >> task_200810072143_0004_r_000033_0 failed to report status for 600 
> >> seconds. Killing!
> Looks like we missed reporting progress in a few places.

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


[jira] Updated: (PIG-475) "task failed to report status" error

Posted by "Shravan Matthur Narayanamurthy (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PIG-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shravan Matthur Narayanamurthy updated PIG-475:
-----------------------------------------------

    Status: Patch Available  (was: Open)

Had missed initializing the PhysicalOperator.reporter in PigMapReduce.Reduce.reduce

> "task failed to report status" error
> ------------------------------------
>
>                 Key: PIG-475
>                 URL: https://issues.apache.org/jira/browse/PIG-475
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: types_branch
>            Reporter: Olga Natkovich
>            Assignee: Shravan Matthur Narayanamurthy
>             Fix For: types_branch
>
>
> When running a very large query a user got the following error after 90 minutes:
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.Launcher
> >> - Error message from task (reduce) tip_200810072143_0004_r_000033Task
> >> task_200810072143_0004_r_000033_0 failed to report status for 600 
> >> seconds. Killing!
> Looks like we missed reporting progress in a few places.

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


[jira] Updated: (PIG-475) "task failed to report status" error

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

Olga Natkovich updated PIG-475:
-------------------------------

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

patch committed; thanks shravan!

> "task failed to report status" error
> ------------------------------------
>
>                 Key: PIG-475
>                 URL: https://issues.apache.org/jira/browse/PIG-475
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: types_branch
>            Reporter: Olga Natkovich
>            Assignee: Shravan Matthur Narayanamurthy
>             Fix For: types_branch
>
>         Attachments: 475.patch
>
>
> When running a very large query a user got the following error after 90 minutes:
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.Launcher
> >> - Error message from task (reduce) tip_200810072143_0004_r_000033Task
> >> task_200810072143_0004_r_000033_0 failed to report status for 600 
> >> seconds. Killing!
> Looks like we missed reporting progress in a few places.

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


[jira] Updated: (PIG-475) "task failed to report status" error

Posted by "Shravan Matthur Narayanamurthy (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/PIG-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shravan Matthur Narayanamurthy updated PIG-475:
-----------------------------------------------

    Attachment: 475.patch

> "task failed to report status" error
> ------------------------------------
>
>                 Key: PIG-475
>                 URL: https://issues.apache.org/jira/browse/PIG-475
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: types_branch
>            Reporter: Olga Natkovich
>            Assignee: Shravan Matthur Narayanamurthy
>             Fix For: types_branch
>
>         Attachments: 475.patch
>
>
> When running a very large query a user got the following error after 90 minutes:
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.Launcher
> >> - Error message from task (reduce) tip_200810072143_0004_r_000033Task
> >> task_200810072143_0004_r_000033_0 failed to report status for 600 
> >> seconds. Killing!
> Looks like we missed reporting progress in a few places.

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


[jira] Commented: (PIG-475) "task failed to report status" error

Posted by "Shravan Matthur Narayanamurthy (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/PIG-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638004#action_12638004 ] 

Shravan Matthur Narayanamurthy commented on PIG-475:
----------------------------------------------------

The query that cause the error will be helpful than generally looking around where we missed it and it might be that there is a udf which doesn't do reporting. Could you pls attach the script?

> "task failed to report status" error
> ------------------------------------
>
>                 Key: PIG-475
>                 URL: https://issues.apache.org/jira/browse/PIG-475
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: types_branch
>            Reporter: Olga Natkovich
>            Assignee: Shravan Matthur Narayanamurthy
>             Fix For: types_branch
>
>
> When running a very large query a user got the following error after 90 minutes:
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.Launcher
> >> - Error message from task (reduce) tip_200810072143_0004_r_000033Task
> >> task_200810072143_0004_r_000033_0 failed to report status for 600 
> >> seconds. Killing!
> Looks like we missed reporting progress in a few places.

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