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

Posted to dev@oozie.apache.org by "Purshotam Shah (JIRA)" <ji...@apache.org> on 2017/04/10 19:03:41 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 ]

Purshotam Shah updated OOZIE-2863:
----------------------------------
    Description: 
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.

> 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
>
> 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.3.15#6346)