hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suraj Menon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-789) BspPeer launched fail because port is bound by others
Date Wed, 31 Jul 2013 08:57:48 GMT

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

Suraj Menon commented on HAMA-789:

Yes we need that change, I shall make it. Currently though initializeSyncService is reading
from the peerAddress value.

syncClient.register(taskId.getJobID(), taskId, peerAddress.getHostName(),
> 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message