[
https://issues.apache.org/jira/browse/KAFKA-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Fung updated KAFKA-306:
----------------------------
Attachment: kafka-306-v1.patch
Broker Failure Test is broken in Kafka 0.8 branch. This patch is fixing the
issues and contains the following changes:
1. All server_*.properties are updated such that the first brokerid is starting
from '0'
2. All mirror_producer*.properties are updated to use zk.connect (and not
broker.list)
3. After the source brokers cluster is started, call
kafka.admin.CreateTopicCommand to create topic.
Currently this patch is working with branch 0.8 (rev. 1342841 patched with
KAFKA-46) with the following workarounds:
1. Before starting the target brokers cluster, start and stop one target broker
to eliminate the following error:
org.I0Itec.zkclient.exception.ZkNoNodeException:
org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode =
NoNode for /brokers/ids
2. The argument "--consumer-timeout-ms" doesn't seem to work properly. The
consumer processes will be terminated manually
3. Consumer Lag info is not available from Zookeeper. Therefore, extra sleep
time is added to the test to wait for the complete consumption of messages
The above issues are being investigated.
> 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
>
>
> 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
