You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2012/11/29 23:44:58 UTC

[jira] [Commented] (OOZIE-1073) Optimize latest and future EL resolution in case of start-instance and end-instance

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

Rohini Palaniswamy commented on OOZIE-1073:
-------------------------------------------

Review request in https://reviews.apache.org/r/8283/. Removed the patch with fix for bug in latest and future when the oozie processing timezone was different than UTC. Handling that in a separate jira - OOZIE-1106.
                
> Optimize latest and future EL resolution in case of start-instance and end-instance
> -----------------------------------------------------------------------------------
>
>                 Key: OOZIE-1073
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1073
>             Project: Oozie
>          Issue Type: Improvement
>            Reporter: Rohini Palaniswamy
>         Attachments: OOZIE-1073-1.patch
>
>
> <start-instance>${coord:latest(-23)}</start-instance>
> <end-instance>${coord:latest(0)}</end-instance>
> Assuming all 24 instances are available, Oozie makes 300(1+2+3+..24) calls instead of 24 calls. This leads to some very high CPU usage when number of latest instances is high.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira