falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-991) consolidate get coord actions in OozieWorkflowEngine
Date Thu, 04 Jun 2015 05:36:38 GMT

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

Ajay Yadava commented on FALCON-991:
------------------------------------

{quote}
Would retrieving all the coord actions for a coord cause OOM within Falcon with this change
? From the looks of it, this wont be any worser than what it was before this. Please confirm
{quote}
It won't be any worse than before.

I will add the exception to the log statement, sorry about the oversight.

> consolidate get coord actions in OozieWorkflowEngine
> ----------------------------------------------------
>
>                 Key: FALCON-991
>                 URL: https://issues.apache.org/jira/browse/FALCON-991
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Shwetha G S
>            Assignee: Ajay Yadava
>         Attachments: FALCON-991-v1.patch, FALCON-991-v2.patch, FALCON-991.patch
>
>
> OozieWorkflowEngine.getCoordActions() gets instances by calling oozieclient.getCoordAction()
for each action. Its not efficient to call oozie API for each instance. Instead, doSummaryJobAction()
gets all instances in bulk using oozieclient.getCoordJobInfo(). But this uses offset which
won't work with purging of coord actions. A new API was added in oozie to get coord actions
between timestamps. We should use that for both usecases



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message