incubator-oozie-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mona Chitnis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OOZIE-597) Issues in Oozie-Hadoop.next/0.23 integration
Date Fri, 04 Nov 2011 18:05:52 GMT

    [ https://issues.apache.org/jira/browse/OOZIE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144216#comment-13144216
] 

Mona Chitnis commented on OOZIE-597:
------------------------------------

1. Oozie is receiving a callback query from Hadoop indicating the submitted job has reached
its end state
(SUCCEEDED/FAILED) following which, Oozie will check with that job_id with the ResourceManager
for status.

At this point in time, the RM logs start showing this after every 10 seconds

Call: protocol=org.apache.hadoop.yarn.proto.ClientRMProtocol.ClientRMProtocolService.BlockingInterface,
method=getApplicationReport

Need more clarity on how the RM handles this incoming request about job status. Does the 10
second re-occurrence
of the above statement point to an RM-specific polling interval? It seems that the Oozie server
thread which is
checking this keeps spinning on this call to the RM.

2. MR job submitted via Oozie gets the external ID which is something of the form "job_0123456_001".
Note the
"job_" prefix. Now looking through the RM web console for the submitted jobs, we see IDs of
the form
"application_0123456_001" corresponding to that job. Need to address this discrepancy for
consequences.

                
> Issues in Oozie-Hadoop.next/0.23 integration
> --------------------------------------------
>
>                 Key: OOZIE-597
>                 URL: https://issues.apache.org/jira/browse/OOZIE-597
>             Project: Oozie
>          Issue Type: Task
>            Reporter: Mohammad Kamrul Islam
>
> Oozie team at Y! is working to make upcoming hadoop release working.
> Since Hadoop 0.23 is a big overhaul, the integration task is very large as well.
>  
> This JIRA is to : 
> * Track the updates of the integration status.
> * Exchange error details and solicit help from others.
> * It primarily verifies if the ___existing___ features work properly.
> * It ___doesn't___ verify the __new__ features added into 0.23. There is a separate JIRA
for new feature support (Ref #Oozie-477).
> Current status:
> * Our dev and QE already made some progress and more work is in progress.
> * Mona (from dev) and Marcy and Michelle (from QE) are actively working and expected
to update this JIRA with status/issues.
>   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message