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 (Resolved) (JIRA)" <ji...@apache.org> on 2011/12/21 08:50:30 UTC

[jira] [Resolved] (HAMA-489) Check port availability before forking child process

     [ 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