[
https://issues.apache.org/jira/browse/KAFKA-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-440:
----------------------------
Attachment: kafka-440-v5.patch
Hi Neha,
Thanks for reviewing the patch. I have fixed the issue and upload the fix in
kafka-440-v5.patch.
Please do the following after downloading the patch:
1. Please add the following log4j settings to
<kafka_home>/config/log4j.properties to allow ProducerPerformance to print out
MessageID
log4j.logger.kafka.perf=DEBUG
log4j.logger.kafka.perf.ProducerPerformance$ProducerThread=DEBUG
2. Please update <kafka_home>/system_test/cluster_config.json for the following
attributes specific to you local machine:
hostname
kafka_home
java_home
3. To turn on debug logging, update
<kafka_home>/system_test/system_test_runner.py:
#namedLogger.setLevel(logging.INFO)
namedLogger.setLevel(logging.DEBUG)
> Create a regression test framework for distributed environment testing
> ----------------------------------------------------------------------
>
> Key: KAFKA-440
> URL: https://issues.apache.org/jira/browse/KAFKA-440
> Project: Kafka
> Issue Type: Task
> Reporter: John Fung
> Assignee: John Fung
> Labels: replication-testing
> Fix For: 0.8
>
> Attachments: kafka-440-v1.patch, kafka-440-v2.patch,
> kafka-440-v3.patch, kafka-440-v5.patch
>
>
> Initial requirements:
> 1. The whole test framework is preferably coded in Python (a common scripting
> language which has well supported features)
> 2. Test framework driver should be generic (distributed environment can be
> local host)
> 3. Test framework related configurations are defined in JSON format
> 4. Test environment, suite, case definitions may be defined in the following
> levels:
> 4-a entity_id is used as a key for looking up related config from different
> levels
> 4-b Cluster level defines: entity_id, hostname, kafka_home, java_home, ...
> 4-c Test suite / case level defines:
> 4-c-1 zookeeper: entity_id, clientPort, dataDir, log_filename,
> config_filename
> 4-c-2 broker: entity_id, port, log.file.size, log.dir, log_filename,
> config_filename
> 4-c-3 producer: entity_id, topic, threads, compression-codec,
> message-size, log_filename, config_filename
--
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
