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, 04 Sep 2012 23:03:07 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-v1.patch

Uploaded kafka-449-v1.patch with the following changes:

1. KAFKA-449: Support Leader Election Testcase for the following items:
1.a no. of iterations on bouncing the leader
1.b record the leader election latency
1.c configurable no. of partitions
1.d configurable no. of replication factor

2. KAFKA-482: Make producer to run during the entire duration of test. This is achieved by
launching the function of calling producer in a thread. When all the bouncing iterations are
done, an environment variable will be updated to signal producer to stop.

3. KAFKA-494: Relative paths should be used for svg URLs in dashboards html. This is changed
in order to make the graphic svg files to be accessible from inside a Hudson build report.
> 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
>   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