[
https://issues.apache.org/jira/browse/OOZIE-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mona Chitnis updated OOZIE-1933:
--------------------------------
Attachment: sla_unit_tests-1.patch
updated patch to include another broken testcase. All other failed tests pass
locally and are known to be flaky
Test run:
{code}
Results :
Failed tests:
testCoordinatorActionCommandsSubmitAndStart(org.apache.oozie.sla.TestSLAEventGeneration)
testRecovery(org.apache.oozie.action.hadoop.TestJavaActionExecutor):
expected:<[SUCCEED]ED> but was:<[FAILED/KILL]ED>
testCoordStatusTransitServiceBackwardSupport(org.apache.oozie.service.TestStatusTransitService)
Tests in error:
testOnJobEvent(org.apache.oozie.sla.TestSLAJobEventListener): invalid child
id [wa1]
testActionReuseWfJobAppPath(org.apache.oozie.command.wf.TestActionStartXCommand):
E0607: Other error in operation [action.start], null
testWorkflowRun(org.apache.oozie.command.wf.TestLastModified):
org.apache.oozie.DagEngineException: E0607: Other error in operation [start],
null
testSucJobPurgeXCommand(org.apache.oozie.command.TestPurgeXCommand): E0604:
Job does not exist [0000001-140717193440158-oozie-chit-W]
testSucCoordPurgeXCommand(org.apache.oozie.command.TestPurgeXCommand): E0604:
Job does not exist [0000000-140717193442386-oozie-chit-C]
{code}
> 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
>
> Attachments: OOZIE-1933-3.patch, OOZIE-1933-4-1.patch,
> sla_unit_tests-1.patch, sla_unit_tests.patch
>
>
> 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)
