helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthiek (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HELIX-578) NPE while deleting a job from a recurrent job queue
Date Tue, 17 Mar 2015 01:37:38 GMT
Karthiek created HELIX-578:
------------------------------

             Summary: NPE while deleting a job from a recurrent job queue
                 Key: HELIX-578
                 URL: https://issues.apache.org/jira/browse/HELIX-578
             Project: Apache Helix
          Issue Type: Bug
            Reporter: Karthiek
            Priority: Critical


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)

Mime
View raw message