mirror of https://github.com/apache/kafka.git
KAFKA-18905; Disable idempotent producer to remove test flakiness (#19644)
As a result of KAFKA-18905 the reassign test will often have test failures which are unrelated to the actual reassignment of partitions. This failure is mentioned in KAFKA-9199. Quote from KAFKA-9199: "This issue popped up in the reassignment system test. It ultimately caused the test to fail because the producer was stuck retrying the duplicate batch repeatedly until ultimately giving up." Disabling the idempotent producer circumvents this issue and allows the reassignment system tests to succeed reliably. The reassignment test still check that produce batches were not lost. Reviewers: José Armando García Sancio <jsancio@apache.org>
This commit is contained in:
parent
7b8633e36f
commit
13fa4537f5
|
@ -163,7 +163,8 @@ class ReassignPartitionsTest(ProduceConsumeValidateTest):
|
|||
self.producer = VerifiableProducer(self.test_context, self.num_producers,
|
||||
self.kafka, self.topic,
|
||||
throughput=self.producer_throughput,
|
||||
enable_idempotence=True,
|
||||
# Once KAFKA-18905 is fixed, the idempotent producer should be enabled.
|
||||
enable_idempotence=False,
|
||||
# This test aims to verify the reassignment without failure, assuming that all partitions have data.
|
||||
# To avoid the reassignment behavior being affected by the `BuiltInPartitioner` (due to the key not being set),
|
||||
# we set a key for the message to ensure both even data distribution across all partitions.
|
||||
|
@ -174,5 +175,6 @@ class ReassignPartitionsTest(ProduceConsumeValidateTest):
|
|||
message_validator=is_int,
|
||||
consumer_properties=consumer_group.maybe_set_group_protocol(group_protocol))
|
||||
|
||||
self.enable_idempotence=True
|
||||
# Once KAFKA-18905 is fixed, the idempotent producer should be enabled.
|
||||
self.enable_idempotence = False
|
||||
self.run_produce_consume_validate(core_test_action=lambda: self.reassign_partitions(bounce_brokers))
|
||||
|
|
Loading…
Reference in New Issue