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/11/09 23:52:21 UTC
[jira] [Created] (HAMA-471) Peer names should be sorted by task id
Peer names should be sorted by task id
--------------------------------------
Key: HAMA-471
URL: https://issues.apache.org/jira/browse/HAMA-471
Project: Hama
Issue Type: Improvement
Reporter: Thomas Jungblut
Like I already thought in here https://issues.apache.org/jira/browse/HAMA-443?focusedCommentId=13146953&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13146953
We need to sort the peer names by task id, because this is the only "constant" thing in this system. And it is consistent with the partitioning id, which makes the examples a lot more easier.
--
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-471) Peer names should be sorted by task
id
Posted by "Edward J. Yoon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147578#comment-13147578 ]
Edward J. Yoon commented on HAMA-471:
-------------------------------------
+1
> Peer names should be sorted by task id
> --------------------------------------
>
> Key: HAMA-471
> URL: https://issues.apache.org/jira/browse/HAMA-471
> Project: Hama
> Issue Type: Improvement
> Reporter: Thomas Jungblut
> Assignee: Thomas Jungblut
> Attachments: HAMA-471.patch
>
>
> Like I already thought in here https://issues.apache.org/jira/browse/HAMA-443?focusedCommentId=13146953&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13146953
> We need to sort the peer names by task id, because this is the only "constant" thing in this system. And it is consistent with the partitioning id, which makes the examples a lot more easier.
--
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-471) Peer names should be sorted by task
id
Posted by "Thomas Jungblut (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147349#comment-13147349 ]
Thomas Jungblut commented on HAMA-471:
--------------------------------------
Generally, the task id will be part of the peername znode in zookeeper (byte array stuff).
Then I read things into a treemap (key taskid, value real peername), pop out the values one by one and but it into an array.
I provide a patch tomorrow.
> Peer names should be sorted by task id
> --------------------------------------
>
> Key: HAMA-471
> URL: https://issues.apache.org/jira/browse/HAMA-471
> Project: Hama
> Issue Type: Improvement
> Reporter: Thomas Jungblut
> Assignee: Thomas Jungblut
>
> Like I already thought in here https://issues.apache.org/jira/browse/HAMA-443?focusedCommentId=13146953&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13146953
> We need to sort the peer names by task id, because this is the only "constant" thing in this system. And it is consistent with the partitioning id, which makes the examples a lot more easier.
--
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] [Resolved] (HAMA-471) Peer names should be sorted by task id
Posted by "Thomas Jungblut (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Jungblut resolved HAMA-471.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.4.0
Thanks for your fast review.
> Peer names should be sorted by task id
> --------------------------------------
>
> Key: HAMA-471
> URL: https://issues.apache.org/jira/browse/HAMA-471
> Project: Hama
> Issue Type: Improvement
> Reporter: Thomas Jungblut
> Assignee: Thomas Jungblut
> Fix For: 0.4.0
>
> Attachments: HAMA-471.patch
>
>
> Like I already thought in here https://issues.apache.org/jira/browse/HAMA-443?focusedCommentId=13146953&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13146953
> We need to sort the peer names by task id, because this is the only "constant" thing in this system. And it is consistent with the partitioning id, which makes the examples a lot more easier.
--
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-471) Peer names should be sorted by task
id
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148284#comment-13148284 ]
Hudson commented on HAMA-471:
-----------------------------
Integrated in Hama-Nightly #349 (See [https://builds.apache.org/job/Hama-Nightly/349/])
[HAMA-471] Peer names should be sorted by task id
tjungblut :
Files :
* /incubator/hama/trunk/CHANGES.txt
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/LocalBSPRunner.java
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/sync/SyncClient.java
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/sync/ZooKeeperSyncClientImpl.java
> Peer names should be sorted by task id
> --------------------------------------
>
> Key: HAMA-471
> URL: https://issues.apache.org/jira/browse/HAMA-471
> Project: Hama
> Issue Type: Improvement
> Reporter: Thomas Jungblut
> Assignee: Thomas Jungblut
> Fix For: 0.4.0
>
> Attachments: HAMA-471.patch
>
>
> Like I already thought in here https://issues.apache.org/jira/browse/HAMA-443?focusedCommentId=13146953&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13146953
> We need to sort the peer names by task id, because this is the only "constant" thing in this system. And it is consistent with the partitioning id, which makes the examples a lot more easier.
--
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-471) Peer names should be sorted by task id
Posted by "Thomas Jungblut (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Jungblut updated HAMA-471:
---------------------------------
Attachment: HAMA-471.patch
This patch addresses this issue.
Test cases running fine.
{noformat}
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Hama parent POM ............................ SUCCESS [3.864s]
[INFO] Apache Hama Core .................................. SUCCESS [1:17.241s]
[INFO] Apache Hama Graph Package ......................... SUCCESS [0.817s]
[INFO] Apache Hama Examples .............................. SUCCESS [12.576s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
{noformat}
> Peer names should be sorted by task id
> --------------------------------------
>
> Key: HAMA-471
> URL: https://issues.apache.org/jira/browse/HAMA-471
> Project: Hama
> Issue Type: Improvement
> Reporter: Thomas Jungblut
> Assignee: Thomas Jungblut
> Attachments: HAMA-471.patch
>
>
> Like I already thought in here https://issues.apache.org/jira/browse/HAMA-443?focusedCommentId=13146953&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13146953
> We need to sort the peer names by task id, because this is the only "constant" thing in this system. And it is consistent with the partitioning id, which makes the examples a lot more easier.
--
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-471) Peer names should be sorted by task id
Posted by "Thomas Jungblut (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Jungblut reassigned HAMA-471:
------------------------------------
Assignee: Thomas Jungblut
> Peer names should be sorted by task id
> --------------------------------------
>
> Key: HAMA-471
> URL: https://issues.apache.org/jira/browse/HAMA-471
> Project: Hama
> Issue Type: Improvement
> Reporter: Thomas Jungblut
> Assignee: Thomas Jungblut
>
> Like I already thought in here https://issues.apache.org/jira/browse/HAMA-443?focusedCommentId=13146953&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13146953
> We need to sort the peer names by task id, because this is the only "constant" thing in this system. And it is consistent with the partitioning id, which makes the examples a lot more easier.
--
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