Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-3276

Refactor SLACalculatorMemory

Add voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 5.0.0
    • Fix Version/s: None
    • Component/s: core
    • Labels:
      None

      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

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              andras.piros Andras Piros

              Dates

              • Created:
                Updated:

                Issue deployment