[
https://issues.apache.org/jira/browse/KAFKA-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira updated KAFKA-2415:
--------------------------------
Resolution: Fixed
Fix Version/s: 0.8.3
Status: Resolved (was: Patch Available)
Issue resolved by pull request 121
[https://github.com/apache/kafka/pull/121]
> Transient failure in
> LogRecoveryTest.testHWCheckpointWithFailuresMultipleLogSegments
> ------------------------------------------------------------------------------------
>
> Key: KAFKA-2415
> URL: https://issues.apache.org/jira/browse/KAFKA-2415
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Fix For: 0.8.3
>
>
> See transient failure in the test with the following error message.
> kafka.server.LogRecoveryTest >
> testHWCheckpointWithFailuresMultipleLogSegments FAILED
> java.util.NoSuchElementException: None.get
> at scala.None$.get(Option.scala:313)
> at scala.None$.get(Option.scala:311)
> at
> kafka.server.LogRecoveryTest$$anonfun$testHWCheckpointWithFailuresMultipleLogSegments$8.apply$mcZ$sp(LogRecoveryTest.scala:215)
> at kafka.utils.TestUtils$.waitUntilTrue(TestUtils.scala:616)
> at
> kafka.server.LogRecoveryTest.testHWCheckpointWithFailuresMultipleLogSegments(LogRecoveryTest.scala:214)
> It looks the fix is to wait for the new broker to create the replica before
> check its HW.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
