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

John Fung commented on KAFKA-674:
---------------------------------

Test description:
============
1. Start 1 Zookeeper
2. Start a 4-broker cluster (Replication factor = 4, 2 partitions)
3. Keep sending messages to 30 topics by ProducerPerformance
4. Perform rolling bounce on all brokers (Controller is the last broker to 
bounce)
5. Stop ProducerPerformance
6. Start ConsoleConsumer
7. Validate MessageID between Producer side & Consumer side (no data loss in 
all topics)
8. Validate log segment checksums across all replicas:

[/tmp] l kafka_server_1_logs/topic_0001-0/
-rw-r--r-- 1 jfung eng    416 Dec 13 11:18 00000000000000000000.index
-rw-r--r-- 1 jfung eng 298768 Dec 13 11:17 00000000000000000000.log

[/tmp] l kafka_server_2_logs/topic_0001-0/
-rw-r--r-- 1 jfung eng    632 Dec 13 11:19 00000000000000000000.index
-rw-r--r-- 1 jfung eng 561768 Dec 13 11:18 00000000000000000000.log

9. If the no. of topics is changed to 20, there will be no issue.

To run the test:
============
1. Apply the attached patch (no need to rebuild Kafka)
2. Under <Kafka_home>/system_test, run this command:
    $ python -u -B system_test_runner.py 2>&1 | tee system_test_output_`date 
+%s`.log
3. It will execute testcase_9062
4. Data log will be located in /tmp/kafka_server_*_logs
5. Log4j messages logs will be under 
<kafka_home>/system_test/clean_shutdown_testsuite/testcase_9062/logs
                
> Clean Shutdown Testing - Log segments checksums mismatch
> --------------------------------------------------------
>
>                 Key: KAFKA-674
>                 URL: https://issues.apache.org/jira/browse/KAFKA-674
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: John Fung
>            Priority: Critical
>              Labels: replication-testing
>         Attachments: kafka-674-reproduce-issue.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

Reply via email to