[
https://issues.apache.org/jira/browse/KAFKA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Ye updated KAFKA-344:
--------------------------
Attachment: kafka_07_producer_performance.patch
zkclient-0.1.jar
kafka-0.7.0.jar
kafka_344_v1.diff
1. The current system test assume there is kafka 0.7 project at location,
"~/Dev/kafka_0.7" (otherwise you need to specify the kafka 07 location at
"cluster_config.json" file
2. The patch make the replication_testsuite not working because they share the
same cluster_config.json, I've talked with John to create three level cluster
configuration: testcase, testsuite and global level. If configuration file is
found at "testcase" level, the framework won't search the other two level,
otherwise if it's found in testsuite level, the framework won't search the
global level. Will rebase after John added this feature
3. Added a few roles: "broker07", "zookeeper07", "producer_performance07", and
"migration_tool" as specified in the cluster_config.json file
4. add a few functions in Kafka_system_test_utils.py in accordance with the new
roles, like start_zookeeper07(), start_producer_performance07(), etc
5. patch the kafka 07 producer performance, by adding message id to the
produced messages.
6. please manually add the two jar files to
"system_test/migration_tool_testsuite" directory as they cannot be included in
the patch file
> migration tool from 0.7 to 0.8
> ------------------------------
>
> Key: KAFKA-344
> URL: https://issues.apache.org/jira/browse/KAFKA-344
> Project: Kafka
> Issue Type: Sub-task
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Yang Ye
> Priority: Blocker
> Labels: tools
> Fix For: 0.8
>
> Attachments: kafka-0.7.0.jar, kafka_07_producer_performance.patch,
> kafka_344_draft.patch, kafka_344_v1.diff, zkclient-0.1.jar
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> Since 0.8 is a non-backward compatible release, we need a migration tool. One
> way to do that is to have a tool that can mirror data from an 0.7 Kafka
> cluster into an 0.8 Kafka cluster. Once the mirror is set up, we can then
> first migrate the consumers to the 0.8 cluster, followed by the producers.
> After that, we can decommission the 0.7 cluster.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
