hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ChiaHung Lin (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-479) Add Counters to Hama Jobs
Date Mon, 28 Nov 2011 13:08:40 GMT

    [ https://issues.apache.org/jira/browse/HAMA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158408#comment-13158408

ChiaHung Lin commented on HAMA-479:

+1 for the patch, that is a quite acceptable solution. 
The global stuff needs either to be stored in ZK or we are going to propagate this back to
the BSPMaster via statusreports.

> Add Counters to Hama Jobs
> -------------------------
>                 Key: HAMA-479
>                 URL: https://issues.apache.org/jira/browse/HAMA-479
>             Project: Hama
>          Issue Type: New Feature
>            Reporter: Thomas Jungblut
>            Assignee: Edward J. Yoon
>              Labels: bsp
>             Fix For: 0.4.0
>         Attachments: counters.patch
> We should add counters for each Hama job.
> We want to add message counters (bytes transfered, local messages sent, outward messages
sent, time in sync etc.), for the last superstep and summed up for all supersteps. 
> It should be as simple as the from Hadoop provided mechanism with enums.
> We could eventually use zookeeper instead of the jobreport.
> For the SSSP Example it should be useful that the last superstep counters are always
in sync in each task after a superstep. == After barrier left, query zookeeper for the values.

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


View raw message