[
https://issues.apache.org/jira/browse/HELIX-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15504847#comment-15504847
]
ASF GitHub Bot commented on HELIX-635:
--------------------------------------
Github user lei-xia commented on a diff in the pull request:
https://github.com/apache/helix/pull/51#discussion_r79500914
--- Diff: helix-core/src/main/java/org/apache/helix/task/JobConfig.java ---
@@ -272,8 +261,6 @@ public TaskConfig getTaskConfig(String id) {
}
cfgMap.put(JobConfigProperty.TimeoutPerPartition.name(), "" +
_timeoutPerTask);
cfgMap.put(JobConfigProperty.MaxAttemptsPerTask.name(), "" +
_maxAttemptsPerTask);
- cfgMap.put(JobConfigProperty.MaxForcedReassignmentsPerTask.name(),
--- End diff --
same here, Helix still save the value, it is just ignored by the controller.
> GenericTaskAssignmentCalculator does not balance task assignment
> ----------------------------------------------------------------
>
> Key: HELIX-635
> URL: https://issues.apache.org/jira/browse/HELIX-635
> Project: Apache Helix
> Issue Type: Bug
> Components: helix-core
> Reporter: Junkai Xue
> Assignee: Junkai Xue
> Fix For: 0.6.x
>
>
> Currently, GenericTaskAssignmentCalculator using AutoRebalancerStrategy
> compute the assignment mapping. There is a bug that all the tasks from same
> job will be assigned to one node, which is not balanced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
