[
https://issues.apache.org/jira/browse/KAFKA-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neha Narkhede updated KAFKA-734:
--------------------------------
Attachment: kafka-734-v4.patch
More improvements to migration tool -
1. Added a shutdown hook and shutdown logic
2. Changed the design of migration tool as per Jun's suggestion. Basically, it
looks more like the request channel idea from the socket server. The migration
threads are consumers that add to a common producer channel. The producer
threads pull from the common channel and send data across. This ensures that if
one of the producers slow down, the data keeps flowing through rest of the
producers.
3. Didn't get a chance to test this on a large workload, there might be bugs.
> Migration tool needs a revamp, it was poorly written and has many performance
> bugs
> ----------------------------------------------------------------------------------
>
> Key: KAFKA-734
> URL: https://issues.apache.org/jira/browse/KAFKA-734
> Project: Kafka
> Issue Type: Bug
> Components: tools
> Affects Versions: 0.8
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
> Priority: Blocker
> Labels: p1
> Attachments: kafka-734-v1.patch, kafka-734-v2.patch,
> kafka-734-v3.patch, kafka-734-v4.patch
>
>
> Migration tool has a number of problems ranging from poor logging to poor
> design. This needs to be thought through again
--
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
