You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@helix.apache.org by "Xia Lei (JIRA)" <ji...@apache.org> on 2015/03/18 06:58:38 UTC
[jira] [Created] (HELIX-582) NPE while deleting a job from a
recurrent job queue
Xia Lei created HELIX-582:
-----------------------------
Summary: NPE while deleting a job from a recurrent job queue
Key: HELIX-582
URL: https://issues.apache.org/jira/browse/HELIX-582
Project: Apache Helix
Issue Type: Bug
Components: helix-core
Affects Versions: 0.6.4
Reporter: Xia Lei
Helix throws an NPE when we try to delete a job from recurrent job queue.
Partial stacktrace:
java.lang.NullPointerException
at org.apache.helix.task.TaskDriver.deleteJob(TaskDriver.java:295)
Helix is looking for workflow context's current state.
WorkflowContext wCtx = TaskUtil.getWorkflowContext(_propertyStore, queueName);
String workflowState =
(wCtx != null) ? wCtx.getWorkflowState().name() : TaskState.NOT_STARTED.name();
But for a recurring workflow, there is no "state" in the parent workflow's context. Only the scheduled workflows will have a "state". Hence the NPE.
To ensure that queue is stopped, Helix should look at the context of last-scheduled-workflow instead of the parent workflow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)