[
https://issues.apache.org/jira/browse/KAFKA-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434356#comment-13434356
]
Neha Narkhede commented on KAFKA-215:
-------------------------------------
We probably need a JIRA to merge the existing broker_failure and mirroring
system test. Do we have another JIRA or should we use this one ?
> Improve system tests for the mirroring code
> -------------------------------------------
>
> Key: KAFKA-215
> URL: https://issues.apache.org/jira/browse/KAFKA-215
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.7
> Reporter: Neha Narkhede
> Priority: Critical
> Labels: newbie
> Fix For: 0.8
>
>
> Improve the system tests for the mirroring code to *add* the following
> testing scenarios -
> 1. Bounce the mirroring kafka cluster during the test
> 2. Add new topics to the source kafka cluster while the mirror is copying
> data for existing topics
> 3. Bounce the source Kafka cluster during the test
> The point of this improvement is to catch any bugs in the consumer
> rebalancing or the detection of new topics logic. Also, verification code of
> this part of the system test can report on the % of duplicates/ % data loss
> in the mirror cluster. Since Kafka guarantees at least once delivery, small
> percentage of duplicates is ok, but any amount of data loss is a critical bug
--
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
