You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Edward J. Yoon (Created) (JIRA)" <ji...@apache.org> on 2011/12/21 08:09:30 UTC
[jira] [Created] (HAMA-489) Check port availability before forking
child process
Check port availability before forking child process
----------------------------------------------------
Key: HAMA-489
URL: https://issues.apache.org/jira/browse/HAMA-489
Project: Hama
Issue Type: Bug
Components: bsp
Affects Versions: 0.3.0
Reporter: Edward J. Yoon
Assignee: Edward J. Yoon
Fix For: 0.4.0
{code}
for (GroomServerAction action : actions) {
Task t = ((LaunchTaskAction) action).getTask();
int peerPort = (Constants.DEFAULT_PEER_PORT + i);
assignedPeerNames.put(t.getTaskID(), peerPort);
i++;
}
{code}
Increasing naively the number of port will potentially cause "already in use" error. We may need to find next available port.
--
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-489) Check port availability before
forking child process
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174477#comment-13174477 ]
Hudson commented on HAMA-489:
-----------------------------
Integrated in Hama-Nightly #402 (See [https://builds.apache.org/job/Hama-Nightly/402/])
[HAMA-489] Check port availability before forking child process
edwardyoon :
Files :
* /incubator/hama/trunk/CHANGES.txt
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/bsp/GroomServer.java
* /incubator/hama/trunk/core/src/main/java/org/apache/hama/util/BSPNetUtils.java
> Check port availability before forking child process
> ----------------------------------------------------
>
> Key: HAMA-489
> URL: https://issues.apache.org/jira/browse/HAMA-489
> Project: Hama
> Issue Type: Bug
> Components: bsp
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> Fix For: 0.4.0
>
> Attachments: HAMA-489.patch
>
>
> {code}
> for (GroomServerAction action : actions) {
> Task t = ((LaunchTaskAction) action).getTask();
> int peerPort = (Constants.DEFAULT_PEER_PORT + i);
> assignedPeerNames.put(t.getTaskID(), peerPort);
> i++;
> }
> {code}
> Increasing naively the number of port will potentially cause "already in use" error. We may need to find next available port.
--
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] [Reopened] (HAMA-489) Check port availability before forking
child process
Posted by "Edward J. Yoon (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward J. Yoon reopened HAMA-489:
---------------------------------
{code}
2011-12-21 17:47:34,710 INFO org.apache.hama.bsp.GroomServer: Launch 1 tasks.
2011-12-21 17:47:34,710 ERROR org.apache.hama.bsp.GroomServer: Fail to execute directive.
java.lang.ClassCastException: org.apache.hama.bsp.KillTaskAction cannot be cast to org.apache.hama.bsp.LaunchTaskAction
at org.apache.hama.bsp.GroomServer$DispatchTasksHandler.handle(GroomServer.java:153)
at org.apache.hama.bsp.GroomServer$Instructor.run(GroomServer.java:204)
2011-12-21 17:47:34,711 INFO org.apache.hama.bsp.GroomServer: Launch 1 tasks.
2011-12-21 17:47:34,711 ERROR org.apache.hama.bsp.GroomServer: Fail to execute directive.
java.lang.ClassCastException: org.apache.hama.bsp.KillTaskAction cannot be cast to org.apache.hama.bsp.LaunchTaskAction
at org.apache.hama.bsp.GroomServer$DispatchTasksHandler.handle(GroomServer.java:153)
at org.apache.hama.bsp.GroomServer$Instructor.run(GroomServer.java:204)
2011-12-21 17:47:34,712 INFO org.apache.hama.bsp.GroomServer: Launch 1 tasks.
2011-12-21 17:47:34,712 ERROR org.apache.hama.bsp.GroomServer: Fail to execute directive.
java.lang.ClassCastException: org.apache.hama.bsp.KillTaskAction cannot be cast to org.apache.hama.bsp.LaunchTaskAction
at org.apache.hama.bsp.GroomServer$DispatchTasksHandler.handle(GroomServer.java:153)
at org.apache.hama.bsp.GroomServer$Instructor.run(GroomServer.java:204)
2011-12-21 17:47:34,712 INFO org.apache.hama.bsp.GroomServer: Launch 1 tasks.
2011-12-21 17:47:34,712 ERROR org.apache.hama.bsp.GroomServer: Fail to execute directive.
java.lang.ClassCastException: org.apache.hama.bsp.KillTaskAction cannot be cast to org.apache.hama.bsp.LaunchTaskAction
at org.apache.hama.bsp.GroomServer$DispatchTasksHandler.handle(GroomServer.java:153)
at org.apache.hama.bsp.GroomServer$Instructor.run(GroomServer.java:204)
2011-12-21 17:47:34,713 INFO org.apache.hama.bsp.GroomServer: Launch 1 tasks.
2011-12-21 17:47:34,713 ERROR org.apache.hama.bsp.GroomServer: Fail to execute directive.
java.lang.ClassCastException: org.apache.hama.bsp.KillTaskAction cannot be cast to org.apache.hama.bsp.LaunchTaskAction
at org.apache.hama.bsp.GroomServer$DispatchTasksHandler.handle(GroomServer.java:153)
at org.apache.hama.bsp.GroomServer$Instructor.run(GroomServer.java:204)
{code}
> Check port availability before forking child process
> ----------------------------------------------------
>
> Key: HAMA-489
> URL: https://issues.apache.org/jira/browse/HAMA-489
> Project: Hama
> Issue Type: Bug
> Components: bsp
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> Fix For: 0.4.0
>
> Attachments: HAMA-489.patch
>
>
> {code}
> for (GroomServerAction action : actions) {
> Task t = ((LaunchTaskAction) action).getTask();
> int peerPort = (Constants.DEFAULT_PEER_PORT + i);
> assignedPeerNames.put(t.getTaskID(), peerPort);
> i++;
> }
> {code}
> Increasing naively the number of port will potentially cause "already in use" error. We may need to find next available port.
--
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-489) Check port availability before forking
child process
Posted by "Edward J. Yoon (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward J. Yoon resolved HAMA-489.
---------------------------------
Resolution: Fixed
fixed.
> Check port availability before forking child process
> ----------------------------------------------------
>
> Key: HAMA-489
> URL: https://issues.apache.org/jira/browse/HAMA-489
> Project: Hama
> Issue Type: Bug
> Components: bsp
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> Fix For: 0.4.0
>
> Attachments: HAMA-489.patch
>
>
> {code}
> for (GroomServerAction action : actions) {
> Task t = ((LaunchTaskAction) action).getTask();
> int peerPort = (Constants.DEFAULT_PEER_PORT + i);
> assignedPeerNames.put(t.getTaskID(), peerPort);
> i++;
> }
> {code}
> Increasing naively the number of port will potentially cause "already in use" error. We may need to find next available port.
--
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-489) Check port availability before forking
child process
Posted by "Edward J. Yoon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward J. Yoon updated HAMA-489:
--------------------------------
Attachment: HAMA-489.patch
Attach my patch. (P.S., Some codes are came from Apache MINA)
> Check port availability before forking child process
> ----------------------------------------------------
>
> Key: HAMA-489
> URL: https://issues.apache.org/jira/browse/HAMA-489
> Project: Hama
> Issue Type: Bug
> Components: bsp
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> Fix For: 0.4.0
>
> Attachments: HAMA-489.patch
>
>
> {code}
> for (GroomServerAction action : actions) {
> Task t = ((LaunchTaskAction) action).getTask();
> int peerPort = (Constants.DEFAULT_PEER_PORT + i);
> assignedPeerNames.put(t.getTaskID(), peerPort);
> i++;
> }
> {code}
> Increasing naively the number of port will potentially cause "already in use" error. We may need to find next available port.
--
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-489) Check port availability before forking
child process
Posted by "Edward J. Yoon (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward J. Yoon resolved HAMA-489.
---------------------------------
Resolution: Fixed
Tested on my cluster. I just commit this.
> Check port availability before forking child process
> ----------------------------------------------------
>
> Key: HAMA-489
> URL: https://issues.apache.org/jira/browse/HAMA-489
> Project: Hama
> Issue Type: Bug
> Components: bsp
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> Fix For: 0.4.0
>
> Attachments: HAMA-489.patch
>
>
> {code}
> for (GroomServerAction action : actions) {
> Task t = ((LaunchTaskAction) action).getTask();
> int peerPort = (Constants.DEFAULT_PEER_PORT + i);
> assignedPeerNames.put(t.getTaskID(), peerPort);
> i++;
> }
> {code}
> Increasing naively the number of port will potentially cause "already in use" error. We may need to find next available port.
--
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