[
https://issues.apache.org/jira/browse/KAFKA-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353922#comment-14353922
]
Abhishek Nigam commented on KAFKA-2003:
---------------------------------------
Hi Ashish/Gwen,
Can you review KAFKA-1888 patch. I have just updated a cleaned up patch with
all the comments I have gotten so far.
I would prefer if we keep these patches distinct.
a) We could for example commit KAFKA-1888
b) Once Ashish is ready with the new test which covers all 8 combinations of
different versions of producers/consumers and brokers and any additional stuff
he is planning to do you can simply subsume KAFKA-1888.
This would enable us to use this patch here locally till the time we have a
working superset which is represented by this ticket.
> Add upgrade tests
> -----------------
>
> Key: KAFKA-2003
> URL: https://issues.apache.org/jira/browse/KAFKA-2003
> Project: Kafka
> Issue Type: Improvement
> Reporter: Gwen Shapira
> Assignee: Ashish K Singh
>
> To test protocol changes, compatibility and upgrade process, we need a good
> way to test different versions of the product together and to test end-to-end
> upgrade process.
> For example, for 0.8.2 to 0.8.3 test we want to check:
> * Can we start a cluster with a mix of 0.8.2 and 0.8.3 brokers?
> * Can a cluster of 0.8.3 brokers bump the protocol level one broker at a time?
> * Can 0.8.2 clients run against a cluster of 0.8.3 brokers?
> There are probably more questions. But an automated framework that can test
> those and report results will be a good start.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
