[
https://issues.apache.org/jira/browse/KAFKA-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127343#comment-14127343
]
Chris Cope commented on KAFKA-1501:
-----------------------------------
Ugh, this bug was obnoxious! This has bit us a enough times that we had to fix
it. To isolate, I ran the full set of tests on our test farm 100x for trunk and
100x for 0.8.1.
* _trunk_ failed 11/100 times
* _0.8.1_ failed 12/100 times
It's a race condition. The fix is for ZooKeeperTestHarness but I need to rebase
and retest it. Also, I think the failure rate may be related to the underlying
hardware (faster processing = more likely to hit the race condition). I should
have a fix that has been tested with the latest trunk tonight.
> transient unit tests failures due to port already in use
> --------------------------------------------------------
>
> Key: KAFKA-1501
> URL: https://issues.apache.org/jira/browse/KAFKA-1501
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Reporter: Jun Rao
> Labels: newbie
>
> Saw the following transient failures.
> kafka.api.ProducerFailureHandlingTest > testTooLargeRecordWithAckOne FAILED
> kafka.common.KafkaException: Socket server failed to bind to
> localhost:59909: Address already in use.
> at kafka.network.Acceptor.openServerSocket(SocketServer.scala:195)
> at kafka.network.Acceptor.<init>(SocketServer.scala:141)
> at kafka.network.SocketServer.startup(SocketServer.scala:68)
> at kafka.server.KafkaServer.startup(KafkaServer.scala:95)
> at kafka.utils.TestUtils$.createServer(TestUtils.scala:123)
> at
> kafka.api.ProducerFailureHandlingTest.setUp(ProducerFailureHandlingTest.scala:68)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
