[
https://issues.apache.org/jira/browse/HAMA-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090100#comment-13090100
]
Edward J. Yoon commented on HAMA-413:
-------------------------------------
{code}
// Reports to a BSPMaster
for (Map.Entry<TaskAttemptID, TaskInProgress> e : runningTasks
.entrySet()) {
Thread.sleep(REPORT_INTERVAL);
TaskInProgress tip = e.getValue();
TaskStatus taskStatus = tip.getStatus();
if (taskStatus.getRunState() == TaskStatus.State.RUNNING) {
taskStatus.setProgress(taskStatus.getSuperstepCount());
if (!tip.runner.isAlive()) {
if (taskStatus.getRunState() != TaskStatus.State.FAILED) {
taskStatus.setRunState(TaskStatus.State.SUCCEEDED);
}
taskStatus.setPhase(TaskStatus.Phase.CLEANUP);
}
}
doReport(taskStatus);
}
Thread.sleep(REPORT_INTERVAL);
{code}
I noticed that original reporting times are the same.
> Remove limitation on the number of tasks
> ----------------------------------------
>
> Key: HAMA-413
> URL: https://issues.apache.org/jira/browse/HAMA-413
> Project: Hama
> Issue Type: Sub-task
> Components: bsp
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> Fix For: 0.4.0
>
> Attachments: HAMA-413_v01.patch, HAMA-413_v02.patch,
> HAMA-413_v03.patch, HAMA_413_v04.patch
>
>
> By HAMA-410 patch, BSPPeer object will be constructed at child process. Now
> we can just remove limitation on the number of tasks.
> Here's TODO list:
> 1. The number of tasks per groom should be configurable e.g.,
> 'bsp.local.tasks.maximum'.
> 2. The 'totalTaskCapacity' should be calculated at
> BSPMaster.getClusterStatus().
> 3. When scheduling tasks, consider how to allocate them.
> 4. Each BSPPeer should know all created peers of Hama cluster by job. It can
> be listed based on actions of GroomServer.
> 5. In examples, 'cluster.getGroomServers()' can be changed to
> 'cluster.getMaxTasks()'.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
