helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhen Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HELIX-566) TaskDriver#enqueueJob need add Task state model definition if not already in cluster
Date Wed, 04 Feb 2015 23:42:37 GMT

     [ https://issues.apache.org/jira/browse/HELIX-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Zhen Zhang updated HELIX-566:
-----------------------------
    Description: 
The Task state model definition is a new state model we add recently for TaskFramework. For
the old cluster settings where Task state model definition is missing, TaskDriver#enqueueJob
might throw an exception when creating the ideal-state for the job but successfully add the
job to the queue in the Workflow config. 

This leaves the workflow/job config/status inconsistent and may blocks job from being scheduled.

Helix controller needs to check (in TaskDriver#enqueueJob) that if Task state model definition
is missing, it will add it to the cluster automatically.



  was:
The Task state model definition is a new state model we add recently for TaskFramework. For
the old cluster settings where Task state model definition is missing, TaskDriver#enqueueJob
might throw an exception when creating the ideal-state for the job but successfully add the
job to the queue in the Workflow config. 

This leaves the workflow/job config/status inconsistent and may blocks job from being scheduled.

We need to check in TaskDriver#enqueueJob that if Task state model definition is missing,
it will add it to the cluster.




> TaskDriver#enqueueJob need add Task state model definition if not already in cluster
> ------------------------------------------------------------------------------------
>
>                 Key: HELIX-566
>                 URL: https://issues.apache.org/jira/browse/HELIX-566
>             Project: Apache Helix
>          Issue Type: Bug
>            Reporter: Zhen Zhang
>
> The Task state model definition is a new state model we add recently for TaskFramework.
For the old cluster settings where Task state model definition is missing, TaskDriver#enqueueJob
might throw an exception when creating the ideal-state for the job but successfully add the
job to the queue in the Workflow config. 
> This leaves the workflow/job config/status inconsistent and may blocks job from being
scheduled.
> Helix controller needs to check (in TaskDriver#enqueueJob) that if Task state model definition
is missing, it will add it to the cluster automatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message