You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Joel Koshy (JIRA)" <ji...@apache.org> on 2012/08/14 20:19:38 UTC

[jira] [Resolved] (KAFKA-215) Improve system tests for the mirroring code

     [ https://issues.apache.org/jira/browse/KAFKA-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joel Koshy resolved KAFKA-215.
------------------------------

    Resolution: Won't Fix

Should be covered by other jiras in 0.8
                
> 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