[
https://issues.apache.org/jira/browse/HELIX-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777486#comment-16777486
]
Hudson commented on HELIX-794:
------------------------------
FAILURE: Integrated in Jenkins build helix #1600 (See
[https://builds.apache.org/job/helix/1600/])
[HELIX-794] TASK: Fix double-booking of tasks upon Participant (narendly: rev
ddb3690486a631efa9db704531781745d02ee546)
* (add)
helix-core/src/test/java/org/apache/helix/integration/task/TestNoDoubleAssign.java
* (edit)
helix-core/src/main/java/org/apache/helix/task/AbstractTaskDispatcher.java
* (edit) helix-core/src/main/java/org/apache/helix/task/JobDispatcher.java
> TASK: Fix double-booking of tasks upon Participant disconnect
> -------------------------------------------------------------
>
> Key: HELIX-794
> URL: https://issues.apache.org/jira/browse/HELIX-794
> Project: Apache Helix
> Issue Type: Improvement
> Reporter: Hunter L
> Assignee: Hunter L
> Priority: Major
>
> It's been observed in production use cases that when there are transient
> Participant connection issues, the Controller would fail to honor
> maxNumberOfTasksPerInstance limit. That is to say, if the user wants only 1
> task from a job (limit is set to 1), Helix must assign up to 1 task onto an
> instance. But upon short Participant disconnects, we saw 2 tasks in RUNNING
> at the same time.
> The cause for this is the incorrect calculation of jobConfigLimitation in
> AbstractTaskDispatcher. This fixes this by utilizing a Map
> (assignedPartitions) to calculate the correct number of tasks to assign.
> Changelist:
> 1. Modify an internal data structure (assignedPartitions)
> 2. Fix the logic that calculates the number of tasks to assign
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
