[
https://issues.apache.org/jira/browse/OOZIE-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mona Chitnis updated OOZIE-1933:
--------------------------------
Description:
SLACalculatorMemory.addJobStatus()
{code}
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);
{code}
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
was:
SLACalculatorMemory.addJobStatus()
{code}
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);
{code}
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
> SLACalculatorMemory HA changes assume SLARegistrationBean exists for all jobs
> -----------------------------------------------------------------------------
>
> Key: OOZIE-1933
> URL: https://issues.apache.org/jira/browse/OOZIE-1933
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Fix For: trunk
>
>
> SLACalculatorMemory.addJobStatus()
> {code}
> 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);
> {code}
> 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
--
This message was sent by Atlassian JIRA
(v6.2#6252)
