[
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-v4.patch
Hi Jun,
Thanks for reviewing kafka-306-v2.patch.
kafka-306-v4.patch is uploaded with the following changes suggested by you:
21.1 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
21.2 ConsumerOffsetChecker needs to be enhanced for 0.8 and it depends on
KAFKA-313. "sleep" is temporarily used for kafka to catch up with the offset
lags.
21.3 The header is now updated to "#### Starting Kafka Broker / Mirror Maker
Failure Test ####"
21.4 There is a file "checksum.log" generated at the end of the test which will
give the checksums found in producer, source consumer, target consumer logs
22. You may see inconsistent failure in this test due to the issue specified in
KAFKA-370
23. README is updated with the steps for ./sbt package
Thanks,
John
> 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
>
>
> 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
