You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "dengziming (Jira)" <ji...@apache.org> on 2021/02/13 04:05:00 UTC
[jira] [Commented] (KAFKA-12251) Add topic ID support to
StopReplica
[ https://issues.apache.org/jira/browse/KAFKA-12251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284077#comment-17284077 ]
dengziming commented on KAFKA-12251:
------------------------------------
I have some problems when implementing this. In the case of deleting a topic, we will act as below:
# Send UpdateMetadataRequest first to delete TopicMetadata in MetadataCache, and will also delete the mapping info between topicId and topicName.
# Send StopReplicaReqeust to ReplicaManager
The ReplicaManager needs a topicName to stop a replica, so we should get topicName from MetadataCache first, but we have already deleted the mapping info between topicId and topicName in step 1.
Here are some of my solutions:
# Do not delete mapping info when deleting a topic until ReplicaManager has stopped the replica, this is difficult
# Getting the mapping info from zookeeper, this is weird.
# Retry with TopicName when receiving a TopicIdUnknown error, this is also weird.
I want to hear your suggestions first, Thank you, [~jolshan] [~rajinisivaram@gmail.com]
we also
> Add topic ID support to StopReplica
> -----------------------------------
>
> Key: KAFKA-12251
> URL: https://issues.apache.org/jira/browse/KAFKA-12251
> Project: Kafka
> Issue Type: Sub-task
> Reporter: dengziming
> Assignee: dengziming
> Priority: Major
>
> Remove topic name and Add topic id to StopReplicaReq and StopReplicaResp
--
This message was sent by Atlassian Jira
(v8.3.4#803005)