Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-1244 SLA Support in Oozie
  3. OOZIE-1442

Purge rogue and stale entries from history set

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • trunk
    • None
    • None
    • None

    Description

      A database exception can while confirming an END_MISS event in 2 scenarios:
      1) sla end_miss for workflow_action occurring way before action was even inserted into Oozie DB, because of the sla timings provided by user
      2) rogue job in memory map, but actually missing from database

      Such an exception is currently handled to continue with the end_miss event, to proceed with the processing. Removing an entry from tracking, on exception, only caters to case 2 but not case 1 (valid). So something like a purge should be done on SLA Calculator Memory history set to get rid of any rogue entries, and free up resources.

      Attachments

        1. removed_unit_test_section.txt
          0.7 kB
          Mona Chitnis

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. OOZIE-3260 [sla] Remove stale item above max retries on JPA related errors from in-memory SLA map

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              chitnis Mona Chitnis
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: