[
https://issues.apache.org/jira/browse/KAFKA-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14142342#comment-14142342
]
Sriharsha Chintalapani commented on KAFKA-1558:
-----------------------------------------------
[~nehanarkhede] [~junrao] update on the tests.
I ran the above tests in 5 kafka brokers and 3 zookeeper node with 1000 topics
with 3 partitions 3 replication factor.
All these topics being written to and read from simultaneously.
1) after the controller is restarted
topic log files and metadata deleted successfully
2) after a soft failure (can simulate by pausing the jvm for longer that zk
session timeout) of the controller
I am not able to consistently pass this test. I am getting this error
"2014-09-21 01:21:39,101] INFO Partition [my-topic-435,0] on broker 5: Cached
zkVersion [114] not equal to that in zookeeper, skip updating ISR
(kafka.cluster.Partition)"
Initially thought it could be related KAFKA-1382
but from debug logs
"expected Some((Leader:2,ISR:2,LeaderEpoch:4,ControllerEpoch:7)) written
Some((Leader:4,ISR:4,LeaderEpoch:5,ControllerEpoch:9))
(kafka.utils.ReplicationUtils$)"
Leader is different. This is causing the broker to keep on logging these
messages.
I am not sure why it didn't get the leader update. I didn't see any errors in
zookeeper logs.
I'll get more details on this.
3) after a topic's partitions have been reassigned to some other brokers
topic deleted no issues
4) after running a preferred leader command
topic successfully deleted
5) after a topic's partition has been increased
topic and new partition data also deleted
6) controller broker is killed (kill -9)
successfully deleted the topic and metadata. Once the killed controller back
online the logfiles for that topic partition on that broker also got deleted.
I am not able to reproduce ReplicaFetcher issue here that pointed out earlier.
Before I was running tests on vms with low memory . I wasn't able to reproduce
this on these nodes.
> AdminUtils.deleteTopic does not work
> ------------------------------------
>
> Key: KAFKA-1558
> URL: https://issues.apache.org/jira/browse/KAFKA-1558
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.1.1
> Reporter: Henning Schmiedehausen
> Assignee: Sriharsha Chintalapani
> Priority: Blocker
> Fix For: 0.8.2
>
>
> the AdminUtils:.deleteTopic method is implemented as
> {code}
> def deleteTopic(zkClient: ZkClient, topic: String) {
> ZkUtils.createPersistentPath(zkClient,
> ZkUtils.getDeleteTopicPath(topic))
> }
> {code}
> but the DeleteTopicCommand actually does
> {code}
> zkClient = new ZkClient(zkConnect, 30000, 30000, ZKStringSerializer)
> zkClient.deleteRecursive(ZkUtils.getTopicPath(topic))
> {code}
> so I guess, that the 'createPersistentPath' above should actually be
> {code}
> def deleteTopic(zkClient: ZkClient, topic: String) {
> ZkUtils.deletePathRecursive(zkClient, ZkUtils.getTopicPath(topic))
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
