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

ASF GitHub Bot commented on KAFKA-2415:
---------------------------------------

GitHub user becketqin opened a pull request:

    https://github.com/apache/kafka/pull/121

    KAFKA-2415: Fix transient failure in LogRecoveryTest

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/becketqin/kafka KAFKA-2415

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/121.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 #121
    
----
commit 346103c410f0afd875f95770b47a9235e0bf8ed2
Author: Jiangjie Qin <j...@jqin-ld1.linkedin.biz>
Date:   2015-08-07T03:25:57Z

    KAFKA-2415: Fix transient failure in LogRecoveryTest

----


> 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
>
> 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)

Reply via email to