kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Fung (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-449) Leader election test
Date Tue, 11 Sep 2012 19:58:08 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

John Fung updated KAFKA-449:

    Attachment: kafka-449-v2.patch

Thanks Neha for reviewing. Another patch kafka-449-v2.patch has been uploaded with the following

1. Sleep time has been reduced as much as possible
2. The Hudson specific directory should not be in the code. This is reverted to the original
version in metrics.py
3. The INFO logging such as "found log line", "unix timestamp", ... etc has been configured
to DEBUG level.
> Leader election test
> --------------------
>                 Key: KAFKA-449
>                 URL: https://issues.apache.org/jira/browse/KAFKA-449
>             Project: Kafka
>          Issue Type: Sub-task
>    Affects Versions: 0.8
>            Reporter: Neha Narkhede
>            Assignee: John Fung
>              Labels: replication-testing
>         Attachments: kafka-449-v1.patch, kafka-449-v2.patch
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> The goal is to ensure that leader election completely successfully each time and also
record the leader election latency. Setup multiple partitions with a particular replication
factor. The test should take in the number of iterations. In each iteration, it bounces one
server. That server will be the leader for a certain set of partitions.  At the end of the
test, report the leader election latency along with message replication verification. The
test consists of several runs, each with a particular replication factor (between 1 and 6)

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

View raw message