[
https://issues.apache.org/jira/browse/HELIX-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596247#comment-14596247
]
ASF GitHub Bot commented on HELIX-601:
--------------------------------------
Github user jicongrui commented on the pull request:
https://github.com/apache/helix/pull/30#issuecomment-114181050
This is kind of hacky, but helix has no better way to handle it.
The request is something between totally out of order (workflow, no
dependency) and totally order (jobDag, job2 can't run after job1).
The request hope job1 is scheduled before job2, and job2 can be scheduled
even if some participants get stuck on job1
> Allow work flow to schedule dependency jobs in parallel
> -------------------------------------------------------
>
> Key: HELIX-601
> URL: https://issues.apache.org/jira/browse/HELIX-601
> Project: Apache Helix
> Issue Type: New Feature
> Reporter: Congrui Ji
>
> Currently, Helix won't schedule dependency jobs in a same work flow. For
> example, if Job2 depends on Job1, Job2 won't be scheduled until every
> partition of Job1 is completed.
> However, if some participant is very slow, then all dependency jobs is
> waiting for that single participant.
> Helix should be able to schedule multiple jobs according to a parameter.
> A.C.
> 1. Introduce parallel count parameter in work flow and job queue.
> 2. Dependency jobs can be scheduled according to the parameter (Now the
> parameter is always 1, so no parallel)
> 3. If Job2 depends on Job1, Job1 is scheduled before Job2.
> 4. No parallel jobs on the same instance. If a instance is running Job1, it
> won't run Job2 until Job1 is finished.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
