Mailing-List: contact dev-help@hama.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hama.apache.org
Date: Thu, 1 Aug 2013 04:13:48 +0000 (UTC)
From: "MaoYuan Xian (JIRA)" <jira@apache.org>
To: dev@hama.apache.org
Message-ID: <JIRA.12660370.1375097937973.149360.1375330428156@arcas>
In-Reply-To: <JIRA.12660370.1375097937973@arcas>
References: <JIRA.12660370.1375097937973@arcas>
Subject: [jira] [Commented] (HAMA-789) BspPeer launched fail because port is
 bound by others
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

MaoYuan Xian commented on HAMA-789:
-----------------------------------

I can run the job successfully with the patch in my cluster.
                
> 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