[OOZIE-3276] Refactor SLACalculatorMemory

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 5.0.0
• Component/s: core
• Assignee: Unassigned
• Reporter: Andras Piros
• Created: 06/Jun/18 10:19
• Updated: 06/Jun/18 10:20

Description

There are times when SLACalculatorMemory#slaMap, or SLACalculatorMemory#historySet contains stale information causing weird {{Exception}}s like the ones handled by OOZIE-3260.

Let's refactor SLACalculatorMemory:

• to have slaMap be consistent w/ basic workflow, coordinator, or bundle entries anytime, meaning in case these haven't been persisted yet or have already been deleted, no SLA update should be performed
• rework also the public interfaces of SLACalculator not to have slaMap or historySet exposed to outside world
• modify SLACalculatorMemory to have slaMap and historySet updates in parallel

Issue Links

• is related to: OOZIE-3260 [sla] Remove stale item above max retries on JPA related errors from in-memory SLA map