Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-6228

Intermittent test failure in FetchRequestTest.testDownConversionWithConnectionFailure

    XMLWordPrintableJSON

Details

    • Test
    • Status: Resolved
    • Minor
    • Resolution: Cannot Reproduce
    • None
    • None
    • None
    • None

    Description

      From https://builds.apache.org/job/kafka-trunk-jdk8/2219/testReport/junit/kafka.server/FetchRequestTest/testDownConversionWithConnectionFailure/ :

      java.lang.AssertionError: Fetch size too small 42, broker may have run out of memory
      	at org.junit.Assert.fail(Assert.java:88)
      	at org.junit.Assert.assertTrue(Assert.java:41)
      	at kafka.server.FetchRequestTest.kafka$server$FetchRequestTest$$fetch$1(FetchRequestTest.scala:214)
      	at kafka.server.FetchRequestTest$$anonfun$testDownConversionWithConnectionFailure$2.apply(FetchRequestTest.scala:226)
      	at kafka.server.FetchRequestTest$$anonfun$testDownConversionWithConnectionFailure$2.apply(FetchRequestTest.scala:226)
      	at scala.collection.immutable.Range.foreach(Range.scala:160)
      	at kafka.server.FetchRequestTest.testDownConversionWithConnectionFailure(FetchRequestTest.scala:226)
      

      I ran FetchRequestTest locally which passed.

                assertTrue(s"Fetch size too small $size, broker may have run out of memory",
                    size > maxPartitionBytes - batchSize)
      

      The assertion message should include maxPartitionBytes and batchSize which would give us more information.

      Attachments

        Activity

          People

            Unassigned Unassigned
            yuzhihong@gmail.com Ted Yu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: