[OOZIE-1933] SLACalculatorMemory HA changes assume SLARegistrationBean exists for all jobs

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk
• Fix Version/s: 4.1.0
• Assignee: Mona Chitnis
• Reporter: Mona Chitnis
• Created: 15/Jul/14 16:08
• Updated: 09/Dec/14 00:45
• Resolved: 21/Jul/14 19:41

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

Issue Links

• supercedes: OOZIE-1911 SLA calculation in HA mode does wrong bit comparison for 'start' and 'duration'
• links to: ReviewBoard