[
https://issues.apache.org/jira/browse/TWILL-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ali Anwar updated TWILL-173:
----------------------------
Attachment: stdout
stderr
[~chtyim] I don't think this issue is actually fixed. See the stdout and stderr
of an ApplicationMaster for a YarnApplication that failed to start up due to
this BindException.
There was a retry implemented, but it seems like its retrying against the same
port each time.
> Application Master failed with BindException occasionally
> ---------------------------------------------------------
>
> Key: TWILL-173
> URL: https://issues.apache.org/jira/browse/TWILL-173
> Project: Apache Twill
> Issue Type: Bug
> Components: core, yarn
> Affects Versions: 0.6.0-incubating, 0.7.0-incubating
> Reporter: Terence Yim
> Assignee: Terence Yim
> Fix For: 0.8.0
>
> Attachments: stderr, stdout
>
>
> When the AM starts the embedded Kafka, it first generates a random port (by
> creating a server socket), followed by provided that port for the Kafka
> server to bind to. It is possible that after the random port was acquired and
> before Kafka server bind to it, there is another process on the same box that
> took that port.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
