[
https://issues.apache.org/jira/browse/KAFKA-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-306:
----------------------------
Attachment: kafka-306-v5.patch
** In replying to Jun's question about KAFKA-313: in this script, the function
"wait_for_zero_consumer_lag" is calling ConsumerOffsetChecker to get the
Consumer lag value. However, the topic-partition info is changed in 0.8 and
it's not returned correctly in ConsumerOffsetChecker. Please refer to this
comment:
https://issues.apache.org/jira/browse/KAFKA-313?focusedCommentId=13397990&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13397990
** Uploaded kafka-306-v5.patch. Changes made in kafka-306-v5.patch:
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 system test broken on replication branch
> -------------------------------------------------------
>
> Key: KAFKA-306
> URL: https://issues.apache.org/jira/browse/KAFKA-306
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Neha Narkhede
> Assignee: John Fung
> Labels: replication
> Attachments: kafka-306-v1.patch, kafka-306-v2.patch,
> kafka-306-v3.patch, kafka-306-v4.patch, kafka-306-v5.patch
>
>
> The system test in system_test/broker_failure is broken on the replication
> branch. This test is a pretty useful failure injection test that exercises
> the consumer rebalancing feature, various replication features like leader
> election. It will be good to have this test fixed as well as run on every
> checkin to the replication branch
--
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
