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

SLACalculatorMemory HA changes assume SLARegistrationBean exists for all jobs

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: trunk
    • Fix Version/s: 4.1.0
    • Component/s: None
    • Labels:
      None

      Description

      SLACalculatorMemory.addJobStatus()

      else {
                      // jobid might not exist in slaMap in HA Setting
                      SLARegistrationBean slaRegBean = SLARegistrationQueryExecutor.getInstance().get(
                              SLARegQuery.GET_SLA_REG_ALL, jobId);
                      SLASummaryBean slaSummaryBean = SLASummaryQueryExecutor.getInstance().get(SLASummaryQuery.GET_SLA_SUMMARY,
                              jobId);
                      slaCalc = new SLACalcStatus(slaSummaryBean, slaRegBean);
      

      Because of SLA Listener, job notification event triggers this even for jobs with no SLA configured - leading to NPE in the SLACalcStatus constructor and annoying exception stacktraces in logs

      Patch to also include log prefix addition to some SLACalculator log line

        Attachments

        1. OOZIE-1933-unit-tests-fix.patch
          20 kB
          Mona Chitnis
        2. OOZIE-1933-4-1.patch
          24 kB
          Mona Chitnis
        3. OOZIE-1933-3.patch
          23 kB
          Mona Chitnis

          Issue Links

            Activity

              People

              • Assignee:
                chitnis Mona Chitnis
                Reporter:
                chitnis Mona Chitnis
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: