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

John Fung edited comment on KAFKA-341 at 5/29/12 11:04 PM:
-----------------------------------------------------------

This patch has been tested based on the following pre-requisites:
1. Kafka 0.8 branch rev. 1342841
2. KAFKA-46 patch applied

This test will do the following:
1. 3 brokers are started up and have replicas enabled by default (no. of 
replicas should be less than or equal to no. of brokers)
2. The logs will be parsed to find out which broker is the leader
3. The leader will be stopped (currently commented out until KAFKA-350 is fixed)
4. Producer will send out some messages
5. Start the broker which is stopped in step 3 (currently commented out until 
KAFKA-350 is fixed)
6. Repeat Step 2 for all 3 brokers.
7. At the end of the test, it will compare the logs and validate the data file 
checksum
                
      was (Author: jfung):
    This patch has been tested based on the following pre-requisites:
1. Kafka 0.8 branch rev. 1342841
2. KAFKA-46 patch applied

Please note the followings for this patch:
1. It creates a new folder "system_test/single_host_multi_brokers"
2. It starts up 3 brokers and have replicas enabled by default
3. At the end of the test, it will compare the logs and validate the data file 
checksum
4. Currently, the broker failure testing part is commented out. Please 
uncomment that after KAFKA-350 is fixed.
                  
> Create a new single host system test to validate all replicas on 0.8 branch
> ---------------------------------------------------------------------------
>
>                 Key: KAFKA-341
>                 URL: https://issues.apache.org/jira/browse/KAFKA-341
>             Project: Kafka
>          Issue Type: Task
>            Reporter: John Fung
>            Assignee: John Fung
>         Attachments: kafka-341-v1.patch
>
>


--
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

        

Reply via email to