[ https://issues.apache.org/jira/browse/KAFKA-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510791#comment-13510791 ]

John Fung edited comment on KAFKA-652 at 1/16/13 12:36 AM:
-----------------------------------------------------------

This test will be set up as followings:
1. Configure a cluster of 4 brokers (for the convenience of rolling bounce)
2. Start ProducerPerformance to keep sending messages on 20 topics (acks = -1)
3. For each brokerid:
    a. call the following command:
        bin/kafka-run-class.sh kafka.admin.ShutdownBroker
            --broker <id>
            --num.retries <n>
            --zookeeper <zkconnectstr>
            --retry.interval.ms <n>
    b. terminate the broker with kill -15
    c. bring up the broker again
4. Verify if there is data loss with ConsoleConsumer
                
      was (Author: jfung):
    This test will be set up as followings:
1. Configure a cluster of 4 brokers (for the convenience of rolling bounce)
2. Start ProducerPerformance to keep sending messages on 20 topics (acks = -1)
3. For each brokerid:
    a. call the following command:
        bin/kafka-run-class.sh kafka.admin.ShutdownBroker
            --broker <id>
            --num.retries <n>
            --zookeeper <zkconnectstr>
            --retry.interval.ms <n>
            --jmx.url <jmx port>
    b. terminate the broker with kill -15
    c. bring up the broker again
4. Verify if there is data loss with ConsoleConsumer
                  
> Create testcases for clean shut-down
> ------------------------------------
>
>                 Key: KAFKA-652
>                 URL: https://issues.apache.org/jira/browse/KAFKA-652
>             Project: Kafka
>          Issue Type: Task
>            Reporter: John Fung
>         Attachments: kafka-652-v1.patch
>
>
--
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