Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KAFKA-3201: Added rolling upgrade system tests from 0.8 and 0.9 to 0.10 #980

Closed
wants to merge 11 commits into from

Conversation

apovzner
Copy link
Contributor

Three main tests:

  1. Setup: Producer (0.8) → Kafka Cluster → Consumer (0.8)
    First rolling bounce: Set inter.broker.protocol.version = 0.8 and message.format.version = 0.8
    Second rolling bonus, use latest (default) inter.broker.protocol.version and message.format.version
  2. Setup: Producer (0.9) → Kafka Cluster → Consumer (0.9)
    First rolling bounce: Set inter.broker.protocol.version = 0.9 and message.format.version = 0.9
    Second rolling bonus, use latest (default) inter.broker.protocol.version and message.format.version
  3. Setup: Producer (0.9) → Kafka Cluster → Consumer (0.9)
    First rolling bounce: Set inter.broker.protocol.version = 0.9 and message.format.version = 0.9
    Second rolling bonus: use inter.broker.protocol.version = 0.10 and message.format.version = 0.9

Plus couple of variations of these tests using old/new consumer and no compression / snappy compression.

@ijuma
Copy link
Contributor

ijuma commented Mar 7, 2016

@apovzner, who will be reviewing this? @granders and/or @ewencp?

@@ -107,4 +107,4 @@ def test_reassign_partitions(self, bounce_brokers, security_protocol):
self.consumer = ConsoleConsumer(self.test_context, self.num_consumers, self.kafka, self.topic, new_consumer=new_consumer, consumer_timeout_ms=60000, message_validator=is_int)
self.kafka.start()

self.run_produce_consume_validate(core_test_action=self.reassign_partitions(bounce_brokers))
self.run_produce_consume_validate(core_test_action=lambda: self.reassign_partitions(bounce_brokers))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow, nice catch. That's a pretty significant mistake.

@ewencp
Copy link
Contributor

ewencp commented Mar 8, 2016

LGTM

@asfgit asfgit closed this in f6e35de Mar 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants