Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
None
Description
- This issue may be related to
KAFKA-618
- To reproduce the issue:
1. Download the latest 0.8 branch and apply the attached patch
2. In <kafka_home>, execute "./sbt update package"
3. In <kafka_home>/system_test, execute "python -B system_test_runner.py" and it will execute testcase_9051
- The validation output would be as follows:
validation_status :
Unique messages from consumer on [t001] : 0
Unique messages from consumer on [t002] : 0
. . .
Unique messages from consumer on [t019] : 0
Unique messages from consumer on [t020] : 0
Unique messages from producer on [t001] : 1000
Unique messages from producer on [t002] : 1000
. . .
Unique messages from producer on [t018] : 1000
Unique messages from producer on [t019] : 1000
Unique messages from producer on [t020] : 1000
Validate for data matched on topic [t001] : FAILED
Validate for data matched on topic [t002] : FAILED
. . .
Validate for data matched on topic [t019] : FAILED
Validate for data matched on topic [t020] : FAILED
Validate for merged log segment checksum in cluster [source] : PASSED
- However, it will work fine if there are only 10 topics
In system_test/replication_testsuite/testcase_9051/testcase_9051_properties.json, update the following line to 10 topics:
"topic": "t001,t002,t003,t004,t005,t006,t007,t008,t009,t010,t011,t012,t013,t014,t015,t016,t017,t018,t019,t020",
Attachments
Attachments
Issue Links
- is blocked by
-
KAFKA-618 Deadlock between leader-finder-thread and consumer-fetcher-thread during broker failure
- Closed