[
https://issues.apache.org/jira/browse/HAMA-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097384#comment-15097384
]
Behroz Sikander commented on HAMA-900:
--------------------------------------
Yes, the default scheduler uses the former method but that method internally
calls the other method which is using the strategy. Code seems fine. If i am
not wrong.
public synchronized Task obtainNewTask(
Map<String, GroomServerStatus> groomStatuses) {
this.clusterSize = groomStatuses.size();
...
for (TaskInProgress task : tasks) {
if (!task.isRunning() && !task.isComplete()) {
result = obtainNewTask(task, groomStatuses, resources);
break;
}
}
I think implementing a new strategy should work fine.
Further, currently I do not need this because if I need less tasks in my job
then I change the bsp.tasks.maximum to whatever I want and then load is evenly
divided. But if just the interface needs to be implemented then I can give it a
try since I already have the cluster where I can duplicate this issue.
> Rotation task scheduler
> -----------------------
>
> Key: HAMA-900
> URL: https://issues.apache.org/jira/browse/HAMA-900
> Project: Hama
> Issue Type: New Feature
> Components: bsp core
> Reporter: Edward J. Yoon
>
> To spread tasks widely, I need a FIFO job scheduler that assign tasks one at
> a time in rotation of groom servers (a method of dealing cards).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
