You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2012/08/07 19:44:10 UTC

[jira] [Created] (KAFKA-450) Test in sync replica changes due to slow or stuck followers

Neha Narkhede created KAFKA-450:
-----------------------------------

             Summary: Test in sync replica changes due to slow or stuck followers
                 Key: KAFKA-450
                 URL: https://issues.apache.org/jira/browse/KAFKA-450
             Project: Kafka
          Issue Type: Sub-task
    Affects Versions: 0.8
            Reporter: Neha Narkhede
            Assignee: John Fung


In this test, setup couple of partitions with replication factor, say 3. Introduce soft failures that simulate a slow replica and/or stuck replica. Do this for a couple of iterations. At the end, report state changes for all partitions and verify message replication correctness.

--
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

[jira] [Updated] (KAFKA-450) Test in sync replica changes due to slow or stuck followers

Posted by "Joel Koshy (JIRA)" <ji...@apache.org>.

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

Joel Koshy updated KAFKA-450:
-----------------------------

    Priority: Blocker  (was: Major)
    
> Test in sync replica changes due to slow or stuck followers
> -----------------------------------------------------------
>
>                 Key: KAFKA-450
>                 URL: https://issues.apache.org/jira/browse/KAFKA-450
>             Project: Kafka
>          Issue Type: Sub-task
>    Affects Versions: 0.8
>            Reporter: Neha Narkhede
>            Assignee: John Fung
>            Priority: Blocker
>              Labels: replication-testing
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> In this test, setup couple of partitions with replication factor, say 3. Introduce soft failures that simulate a slow replica and/or stuck replica. Do this for a couple of iterations. At the end, report state changes for all partitions and verify message replication correctness.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira