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

["Rohini Palaniswamy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OOZIE-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rohini Palaniswamy updated OOZIE-1073:
--------------------------------------

    Attachment: OOZIE-1073-1.patch

  Attaching initial patch. Newly added tests testActionInputCheckLatest and testActionInputCheckFuture in TestCoordActionInputCheckXCommand fail for the extending test class TestCoordActionInputCheckXCommandNonUTC. This is not due to the newly added code but that of the existing behaviour. Waiting for a clarification from [~tucu00] on what is the expected behaviour in case of latest and future in case of a NonUTC oozie timezone. 
                
> 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