[
https://issues.apache.org/jira/browse/TWILL-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453448#comment-15453448
]
ASF GitHub Bot commented on TWILL-173:
--------------------------------------
GitHub user chtyim opened a pull request:
https://github.com/apache/twill/pull/9
(TWILL-173) Have EmbeddedKafkaServer restart multiple times on bind failure
- Due to potential race condition between random port generation vs actual
binding, there is a possibility that the binding would fail.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chtyim/twill feature/twill-173
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/twill/pull/9.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #9
----
commit ad81f4d73e7161ea676dbb86d2c44b1428f6e976
Author: Terence Yim <[email protected]>
Date: 2016-08-31T21:38:19Z
(TWILL-173) Have EmbeddedKafkaServer restart multiple times on bind failure
- Due to potential race condition between random port generation vs actual
binding, there is a possibility that the binding would fail.
----
> 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
> Fix For: 0.8.0
>
>
> 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.4#6332)
