[
https://issues.apache.org/jira/browse/KAFKA-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406067#comment-13406067
]
John Fung edited comment on KAFKA-306 at 7/3/12 11:01 PM:
----------------------------------------------------------
Uploaded kafka-306-v6.patch and made further changes in ProducerPerformance and
ConsoleConsumer to support producing sequential message IDs such that it would
be easier to troubleshoot data loss.
ProducerPerformance.scala
* Added command line option "--seq-id-starting-from". This option enable
"seqIdMode" with the following changes:
* Every message will be tagged with a sequential message ID such that all
IDs are unique
* Every message will be sent by its own producer thread sequentially
* Each producer thread will use a unique range of numbers to give
sequential message IDs
* All message IDs are leftpadded with 0s for easier troubleshooting
* Extra characters are added to the message to make up the required message
size
ConsoleConsumer.scala
* Added DecodedMessageFormatter class to display message contents
run-test.sh
* Modified to use the enhanced ProducerPerformance and ConsoleConsumer
* Validate "MessageID" instead of "checksum" for data matching between
source and target consumers
was (Author: jfung):
Uploaded kafka-306-v6.patch and the changes are as follows:
ProducerPerformance.scala
* Added command line option "--seq-id-starting-from". This option enable
"seqIdMode" with the following changes:
* Every message will be tagged with a sequential message ID such that all
IDs are unique
* Every message will be sent by its own producer thread sequentially
* Each producer thread will use a unique range of numbers to give
sequential message IDs
* All message IDs are leftpadded with 0s for easier troubleshooting
* Extra characters are added to the message to make up the required message
size
ConsoleConsumer.scala
* Added DecodedMessageFormatter class to display message contents
run-test.sh
* Modified to use the enhanced ProducerPerformance and ConsoleConsumer
* Validate "MessageID" instead of "checksum" for data matching between
source and target consumers
> broker failure system test broken on replication branch
> -------------------------------------------------------
>
> Key: KAFKA-306
> URL: https://issues.apache.org/jira/browse/KAFKA-306
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Neha Narkhede
> Assignee: John Fung
> Labels: replication
> Attachments: kafka-306-v1.patch, kafka-306-v2.patch,
> kafka-306-v3.patch, kafka-306-v4.patch, kafka-306-v5.patch, kafka-306-v6.patch
>
>
> The system test in system_test/broker_failure is broken on the replication
> branch. This test is a pretty useful failure injection test that exercises
> the consumer rebalancing feature, various replication features like leader
> election. It will be good to have this test fixed as well as run on every
> checkin to the replication branch
--
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
