From 4fa8af9470bc932ed5f66d53a981f6792abf92a6 Mon Sep 17 00:00:00 2001 From: Ewen Cheslack-Postava Date: Wed, 25 Feb 2015 15:26:43 -0800 Subject: [PATCH] KAFKA-1881: Fix out of memory error in testDeleteTopicWithCleaner by making the dedupe buffer much smaller. --- core/src/test/scala/unit/kafka/admin/DeleteTopicTest.scala | 2 ++ 1 file changed, 2 insertions(+) diff --git a/core/src/test/scala/unit/kafka/admin/DeleteTopicTest.scala b/core/src/test/scala/unit/kafka/admin/DeleteTopicTest.scala index 0cbd726..c8f336a 100644 --- a/core/src/test/scala/unit/kafka/admin/DeleteTopicTest.scala +++ b/core/src/test/scala/unit/kafka/admin/DeleteTopicTest.scala @@ -230,6 +230,8 @@ class DeleteTopicTest extends JUnit3Suite with ZooKeeperTestHarness { brokerConfigs(0).setProperty("log.cleanup.policy","compact") brokerConfigs(0).setProperty("log.segment.bytes","100") brokerConfigs(0).setProperty("log.segment.delete.delay.ms","1000") + brokerConfigs(0).setProperty("log.cleaner.dedupe.buffer.size","1048577") + val servers = createTestTopicAndCluster(topic,brokerConfigs) // for simplicity, we are validating cleaner offsets on a single broker -- 2.2.1