[
https://issues.apache.org/jira/browse/KAFKA-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479328#comment-13479328
]
John Fung commented on KAFKA-573:
---------------------------------
A full regression test (35 test cases) has been launched with this patch and
the following is the summary of the results:
1. There are all together 5 failures in 5 test cases out of 35 cases.
* testcase_0103 : 2 out of 2300 msg lost (checksum matched) - failure case
with Ack == 1 in Sync mode (1 topic, 1 partition)
* testcase_0105 : 2 out of 2300 msg lost (checksum matched) - failure case
with Ack == 1 in Async mode (1 topic, 1 partition)
* testcase_0114 : 11 out of 5100 msg lost (checksum matched) - failure case
with Ack == 1 in Async mode (1 topic, 3 partitions)
* testcase_0117 : 44 out of 5100 msg lost (checksum matched) - failure case
with Ack == 1 in Sync mode (1 topic, 3 partitions)
* testcase_0122 : 1524 out of 4600 msg lost (checksum matched) - failure
case with Ack == 1 in Sync mode ( 2 topics, 3 partitions)
2. The results suggest that the fix for KAFKA-573 is working well (minor data
loss in the first 4 cases are expected in leader failure cases when ack == 1).
3. The result in testcase_0122 could be related to a different issue and a new
JIRA will be created to keep track of that.
> System Test : Leader Failure Log Segment Checksum Mismatched When
> request-num-acks is 1
> ---------------------------------------------------------------------------------------
>
> Key: KAFKA-573
> URL: https://issues.apache.org/jira/browse/KAFKA-573
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: John Fung
> Assignee: Jun Rao
> Fix For: 0.8
>
> Attachments: acks1_leader_failure_data_loss.tar.gz, kafka-573.patch,
> kafka-573-reproduce-issue.patch
>
>
> • Test Description:
> 1. Start a 3-broker cluster as source
> 2. Send messages to source cluster
> 3. Find leader and terminate it (kill -15)
> 4. Start the broker again
> 5. Start a consumer to consume data
> 6. Compare the MessageID in the data between producer log and consumer log.
> • Issue: There will be data loss if request-num-acks is set to 1.
> • To reproduce this issue, please do the followings:
> 1. Download the latest 0.8 branch
> 2. Apply the patch attached to this JIRA
> 3. Build kafka by running "./sbt update package"
> 4. Execute the test in directory "system_test" : "python -B
> system_test_runner.py"
> 5. This test will execute testcase_2 with the following settings:
> Replica factor : 3
> No. of partitions : 1
> No. of bouncing : 1
--
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
