[
https://issues.apache.org/jira/browse/HAMA-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222092#comment-13222092
]
Edward J. Yoon commented on HAMA-515:
-------------------------------------
I'm still think about "Add counting feature to get the total number of message
exchanges", http://markmail.org/thread/eci7y7ihb5xx4v5o
By the way, Each task's some progress can be merged into Job Counters
periodically at updateTaskStatus() method.
{code}
public synchronized void updateTaskStatus(TaskInProgress tip,
TaskStatus taskStatus) {
tip.updateStatus(taskStatus); // update tip
if (superstepCounter < taskStatus.getSuperstepCount()) {
superstepCounter = taskStatus.getSuperstepCount();
// TODO Later, we have to update JobInProgress status here
}
}
{code}
IMO, the total number of supersteps, a total number of msg exchanges, or packet
size should be counted by Job Counters.
> Counter should be synchronized by sync()
> ----------------------------------------
>
> Key: HAMA-515
> URL: https://issues.apache.org/jira/browse/HAMA-515
> Project: Hama
> Issue Type: New Feature
> Affects Versions: 0.4.0
> Reporter: Thomas Jungblut
> Priority: Minor
> Fix For: 0.5.0
>
>
> We should synchronize the counters in all tasks after a sync() call.
> Then someone can use it for flow control. E.G. graph related algorithms, to
> get the number of globally updated vertices.
> Two options to solve this:
> - Sync the whole stuff over RPC from the BSPMaster
> - Use Zookeeper for counter handling
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
