[
https://issues.apache.org/jira/browse/KAFKA-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-373:
----------------------------
Attachment: kafka-373-v2.patch
Hi Joel,
Thanks for reviewing this patch.
Uploaded kafka-373-v2.patch and here are the changes:
1. In "initialize" function, added code to find the location of the zk & kafka
log4j log files.
2. In "cleanup" function, added code to remove the zk & kafka log4j log files
3. The header of the script is now removed and the description are in README
4. Use getopt to process command line arguments
5. Consolidated the following functions:
* start_console_consumer_for_source_producer
* start_console_consumer_for_mirror_producer
* wait_for_zero_source_console_consumer_lags
* wait_for_zero_mirror_console_consumer_lags
6. The file to notify producer to stop:
The producer is sent to the background to run in a while-loop. If a file is
used to notify the producer process in the background, the producer will exit
properly inside the while loop.
7. The following check is required for each of the source, target and mirror
maker. It is because the following 2 lines are needed for:
* Line 1: find out if the $bounce_source_id is a char in the string
$svr_to_bounce
* Line 2: check to see if $num_iterations is already reached and if
$svr_idx > 0 (meaning this server needs to be bounced)
* Line 1: svr_idx=`expr index $svr_to_bounce $bounce_source_id`
* Line 2: if [[ $num_iterations -ge $iter && $svr_idx -gt 0 ]]; then
> Broker Failure Test needs to be fixed to work with Mirror Maker in TRUNK
> ------------------------------------------------------------------------
>
> Key: KAFKA-373
> URL: https://issues.apache.org/jira/browse/KAFKA-373
> Project: Kafka
> Issue Type: Task
> Reporter: John Fung
> Assignee: John Fung
> Attachments: kafka-373-v1.patch, kafka-373-v2.patch
>
>
> Embedded consumer is no longer supported and Mirror Maker is introduced to
> TRUNK. Broker Failure test needs to be fixed to use Mirror Maker for
> mirroring.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
