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 Mon, 27 Apr 2015 04:39:38 GMT

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

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

[~sriksun] 

I didn't understand the "stuck in the first 1000 instances" part. Do you suspect first 1000
results will take a long time to return? The pagination is implemented in the oozie side and
not falcon side and we have been using it for some time, so I assumed that it will work fine.



> 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.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