[
https://issues.apache.org/jira/browse/OOZIE-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976096#comment-15976096
]
Satish Subhashrao Saley commented on OOZIE-2863:
------------------------------------------------
bq.Test failures are related to OOZIE-2457.
No, this is due to OOZIE-2815. Tests are failing because Services singleton was
null. It depends on the sequence of tests run, so sometimes we see success
while running these tests with other tests. It needs to be fixed by
initializing services.
> 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
> 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.3.15#6346)
