You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Satish Subhashrao Saley (JIRA)" <ji...@apache.org> on 2017/12/09 02:02:03 UTC

[jira] [Updated] (OOZIE-2863) SLACalculatorMemory.loadOnRestart causing delay in server start

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

Satish Subhashrao Saley updated OOZIE-2863:
-------------------------------------------

Cherry-picked from master to branch-4.3.


> SLACalculatorMemory.loadOnRestart causing delay in server start
> ---------------------------------------------------------------
>
>                 Key: OOZIE-2863
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2863
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Purshotam Shah
>            Assignee: Purshotam Shah
>             Fix For: 4.3.1
>
>         Attachments: OOZIE-2863-V2.patch
>
>
> LoadOnRestart load all job and tries to calculate SLA status. Based on job and SLA status, it moves job into historyMap or slaMap.
> Mostly, the slowness is caused by calculating SLA status (since it needs to acquire ZK lock and make DB calls for each SLA job modified in last seven days).
> LoadOnRestart should only populate slaMap entry, and periodic SLA check should take care of calculating SLA status.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)