hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-789) BspPeer launched fail because port is bound by others
Date Thu, 06 Feb 2014 12:10:09 GMT

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

Edward J. Yoon commented on HAMA-789:

This patch is totally wrongly implemented. The random port was used to avoid "Address already
in use" exception.

  public static final class BSPPeerChild {

    public static void main(String[] args) throws Throwable {
      peerPort = BSPNetUtils.getNextAvailable(peerPort);

The every child's peerPort always will be 61001, because BSPNetUtils.getNextAvailable() is
called before launching BSPPeer server. Moreover, peerPort was never used.

I'll revert this. :/

> BspPeer launched fail because port is bound by others
> -----------------------------------------------------
>                 Key: HAMA-789
>                 URL: https://issues.apache.org/jira/browse/HAMA-789
>             Project: Hama
>          Issue Type: Bug
>          Components: bsp core
>    Affects Versions: 0.6.2
>            Reporter: MaoYuan Xian
>            Assignee: Suraj Menon
>             Fix For: 0.6.3
>         Attachments: HAMA-789.patch, HAMA-789.patch
> In GroomServer, we call BSPNetUtils.getNextAvailable to assigning the bsppeer listening
port. After figures out an available port, the GroomServer release the port and launches the
BspPeer(Child), then the child listens to this port.
> However, during the GroomServer release the port and peer listens the port, if other
process in the operation system binds to the same port occasionally, the bsppeer will fail
to start up because of "Address already in use" exception.

This message was sent by Atlassian JIRA

View raw message