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

Potential inconsistency between the in-memory SLA map and the Oozie database

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.1.0
    • Component/s: None
    • Labels:
      None

      Description

      Upon SLACalculatorMemory.addRegistration, Oozie puts an entry into an in-memory concurrent hashmap ("slaMap"), and later persists it in the Oozie database.

      However, if there is a failure during the database operation, a JPAExecutorException is thrown, and the entry is not removed from the SLA map.
      It may introduce inconsistency between the Oozie database and the SLA map.

      To prevent this, a rollback mechanism (with proper logging) should be implemented. It would also make sense to do more sanity/consistency check in the Oozie server.

        Attachments

        1. OOZIE-3134-007.patch
          18 kB
          Julia Kinga Marton
        2. OOZIE-3134-006.patch
          18 kB
          Julia Kinga Marton
        3. OOZIE-3134-005.patch
          17 kB
          Julia Kinga Marton
        4. OOZIE-3134-004.patch
          17 kB
          Julia Kinga Marton
        5. OOZIE-3134-003.patch
          17 kB
          Julia Kinga Marton
        6. OOZIE-3134-002.patch
          17 kB
          Julia Kinga Marton
        7. OOZIE-3134-001.patch
          15 kB
          Julia Kinga Marton

          Issue Links

            Activity

              People

              • Assignee:
                kmarton Julia Kinga Marton
                Reporter:
                asasvari Attila Sasvari
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: