kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yang Ye (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-344) migration tool from 0.7 to 0.8
Date Sun, 09 Sep 2012 09:32:07 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Yang Ye updated KAFKA-344:

    Attachment: kafka_344_draft.patch

Sorry the system test is still not done yet. The current system test framework assume a global
"cluster_config.json" file, it's used by all testSuites and all test cases under each suite.
But current cluster config (3 broker, 1 zookeeper, 1 consumer, 1 producer) does not apply
to migration test, so I have to create a new one (1 07 zookeeper, 1 08 zookeeper, 3 07 brokers,
3 08 brokers, 1 07 producer, 1 migration tool, 1 08 consumer), 

But the current replication_testSuite cannot work with this configration, I have to delete
it temporarily. (I've talked with John to enable local cluster configuration instead of just
global one)

I created new "role"s of "broker07", "zookeeper07" and "producer_performance07", and changed
a few files in the system test framework. Currently it is still not working, continuing on

Please help review the migration tool itself
> 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
>              Labels: tools
>             Fix For: 0.8
>         Attachments: kafka_344_draft.patch
>   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

View raw message