[
https://issues.apache.org/jira/browse/KAFKA-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351806#comment-14351806
]
Ashish K Singh commented on KAFKA-2003:
---------------------------------------
[~gwenshap] Based on the discussion here and on KAFKA-1888. I think below is
the action item we agree upon.
1. Kafka system sanity test, "check that everything is ok". Evaluate if
existing system tests can cover this. If not, then can we add to the system
tests. If not, then what would be a good maintainable solution. [~charmalloc]
had some suggestion on KAFKA-1888.
2. Evaluate different options and either reuse existing system test or
create/use some tool to ease testing upgrade and compatibility scenarios.
3. Build rolling upgrade tests using above tools.
[~anigam] I assume you are interested in working on this. Could you update the
status on KAFKA-1888. If the above plan sounds good to you, we can setup a call
to discuss further and come up with a firm plan.
> 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)
