You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Thomas Jungblut (Created) (JIRA)" <ji...@apache.org> on 2011/12/03 18:48:39 UTC

[jira] [Created] (HAMA-484) Counters should be accessible in client

Counters should be accessible in client
---------------------------------------

                 Key: HAMA-484
                 URL: https://issues.apache.org/jira/browse/HAMA-484
             Project: Hama
          Issue Type: Improvement
    Affects Versions: 0.4.0
            Reporter: Thomas Jungblut
             Fix For: 0.5.0


Our counters for each job should be available through the BSPMaster so that the BSPClient can get them.
Optional: We can add this after a job has run to print some statistics.

--
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

        

[jira] [Commented] (HAMA-484) Counters should be accessible in client

Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HAMA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216071#comment-13216071 ] 

Hudson commented on HAMA-484:
-----------------------------

Integrated in Hama-Nightly #465 (See [https://builds.apache.org/job/Hama-Nightly/465/])
    [HAMA-484]: Counters should be accessible in client (tjungblut) (Revision 1293161)

     Result = SUCCESS
tjungblut : 
Files : 
* /incubator/hama/trunk/CHANGES.txt
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/BSPJobClient.java
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/BSPMaster.java
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/BSPPeerImpl.java
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/Counters.java
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/JobInProgress.java
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/JobStatus.java
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/LocalBSPRunner.java
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/RunningJob.java
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/TaskStatus.java

                
> Counters should be accessible in client
> ---------------------------------------
>
>                 Key: HAMA-484
>                 URL: https://issues.apache.org/jira/browse/HAMA-484
>             Project: Hama
>          Issue Type: Improvement
>    Affects Versions: 0.4.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>              Labels: bsp
>             Fix For: 0.5.0
>
>         Attachments: HAMA-484.patch
>
>
> Our counters for each job should be available through the BSPMaster so that the BSPClient can get them.
> Optional: We can add this after a job has run to print some statistics.

--
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

        

[jira] [Commented] (HAMA-484) Counters should be accessible in client

Posted by "Thomas Jungblut (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HAMA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213701#comment-13213701 ] 

Thomas Jungblut commented on HAMA-484:
--------------------------------------

{noformat}
12/02/22 16:22:12 WARN bsp.BSPJobClient: No job jar file set.  User classes may not be found. See BSPJob#setJar(String) or check Your jar file.
12/02/22 16:22:13 INFO bsp.BSPJobClient: Running job: job_localrunner_0001
12/02/22 16:22:13 INFO bsp.LocalBSPRunner: Setting up a new barrier for 10 tasks!
12/02/22 16:22:16 INFO bsp.BSPJobClient: Current supersteps number: 0
12/02/22 16:22:16 INFO bsp.BSPJobClient: The total number of supersteps: 0
12/02/22 16:22:16 INFO bsp.BSPJobClient: Counters: 2
12/02/22 16:22:16 INFO bsp.BSPJobClient:   org.apache.hama.bsp.JobInProgress$JobCounter
12/02/22 16:22:16 INFO bsp.BSPJobClient:     LAUNCHED_TASKS=10
12/02/22 16:22:16 INFO bsp.BSPJobClient:   org.apache.hama.bsp.BSPPeerImpl$PeerCounter
12/02/22 16:22:16 INFO bsp.BSPJobClient:     SUPERSTEP_SUM=10
Estimated value of PI is	3.14608
Job Finished in 3.345 seconds
{noformat}

Looks like this, I have changed the name of the superstep counter to SUPERSTEP_SUM, because it is the sum of supersteps each task did. 

*I haven't tested it in distributed environment yet.*
                
> Counters should be accessible in client
> ---------------------------------------
>
>                 Key: HAMA-484
>                 URL: https://issues.apache.org/jira/browse/HAMA-484
>             Project: Hama
>          Issue Type: Improvement
>    Affects Versions: 0.4.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>              Labels: bsp
>             Fix For: 0.5.0
>
>
> Our counters for each job should be available through the BSPMaster so that the BSPClient can get them.
> Optional: We can add this after a job has run to print some statistics.

--
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

        

[jira] [Updated] (HAMA-484) Counters should be accessible in client

Posted by "Thomas Jungblut (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HAMA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Jungblut updated HAMA-484:
---------------------------------

    Status: Patch Available  (was: Open)

Seems to work.
                
> Counters should be accessible in client
> ---------------------------------------
>
>                 Key: HAMA-484
>                 URL: https://issues.apache.org/jira/browse/HAMA-484
>             Project: Hama
>          Issue Type: Improvement
>    Affects Versions: 0.4.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>              Labels: bsp
>             Fix For: 0.5.0
>
>         Attachments: HAMA-484.patch
>
>
> Our counters for each job should be available through the BSPMaster so that the BSPClient can get them.
> Optional: We can add this after a job has run to print some statistics.

--
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

        

[jira] [Commented] (HAMA-484) Counters should be accessible in client

Posted by "Edward J. Yoon (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HAMA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215273#comment-13215273 ] 

Edward J. Yoon commented on HAMA-484:
-------------------------------------

+1
                
> Counters should be accessible in client
> ---------------------------------------
>
>                 Key: HAMA-484
>                 URL: https://issues.apache.org/jira/browse/HAMA-484
>             Project: Hama
>          Issue Type: Improvement
>    Affects Versions: 0.4.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>              Labels: bsp
>             Fix For: 0.5.0
>
>         Attachments: HAMA-484.patch
>
>
> Our counters for each job should be available through the BSPMaster so that the BSPClient can get them.
> Optional: We can add this after a job has run to print some statistics.

--
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

        

[jira] [Updated] (HAMA-484) Counters should be accessible in client

Posted by "Thomas Jungblut (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HAMA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Jungblut updated HAMA-484:
---------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Thanks, just committed.
                
> Counters should be accessible in client
> ---------------------------------------
>
>                 Key: HAMA-484
>                 URL: https://issues.apache.org/jira/browse/HAMA-484
>             Project: Hama
>          Issue Type: Improvement
>    Affects Versions: 0.4.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>              Labels: bsp
>             Fix For: 0.5.0
>
>         Attachments: HAMA-484.patch
>
>
> Our counters for each job should be available through the BSPMaster so that the BSPClient can get them.
> Optional: We can add this after a job has run to print some statistics.

--
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

        

[jira] [Assigned] (HAMA-484) Counters should be accessible in client

Posted by "Thomas Jungblut (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HAMA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Jungblut reassigned HAMA-484:
------------------------------------

    Assignee: Thomas Jungblut
    
> Counters should be accessible in client
> ---------------------------------------
>
>                 Key: HAMA-484
>                 URL: https://issues.apache.org/jira/browse/HAMA-484
>             Project: Hama
>          Issue Type: Improvement
>    Affects Versions: 0.4.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>              Labels: bsp
>             Fix For: 0.5.0
>
>
> Our counters for each job should be available through the BSPMaster so that the BSPClient can get them.
> Optional: We can add this after a job has run to print some statistics.

--
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

        

[jira] [Updated] (HAMA-484) Counters should be accessible in client

Posted by "Thomas Jungblut (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HAMA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Jungblut updated HAMA-484:
---------------------------------

    Attachment: HAMA-484.patch

I test in distributed enviroment tomorrow.
                
> Counters should be accessible in client
> ---------------------------------------
>
>                 Key: HAMA-484
>                 URL: https://issues.apache.org/jira/browse/HAMA-484
>             Project: Hama
>          Issue Type: Improvement
>    Affects Versions: 0.4.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>              Labels: bsp
>             Fix For: 0.5.0
>
>         Attachments: HAMA-484.patch
>
>
> Our counters for each job should be available through the BSPMaster so that the BSPClient can get them.
> Optional: We can add this after a job has run to print some statistics.

--
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