[BUG] Namespace bundle for topic not served by this instance. Please redo the lookup.

Describe the bug Producer and Consumer throw errors when trying to publish/consume messages from topics created with bin/pulsar-admin and autoCreatedTopics. This error seems to be intermittent, some times when publishing gets an error sometimes seems to be able to publish messages and the same for consumers. Broker has configured brokerDeleteInactiveTopicsEnabled=false

To Reproduce (Our setup is a 3 broker env) Steps to reproduce the behavior:

1. Start up your Pulsar Broker with KOP
2. Create a partitioned topic
3. use bin/kafka-console-producer.sh to send messages
4. use bin/kafka-console-consumer.sh to receive messages

Expected behavior Be able to use it every time the topic created

Screenshots 2022-05-25T23:54:24,792+0000 [pulsar-io-5-3] WARN org.apache.pulsar.broker.service.BrokerService - Namespace bundle for topic (persistent://public/default/angeltest-partition-0) not served by this instance. Please redo the lookup. Request is denied: namespace=public/default 2022-05-25T23:54:24,792+0000 [pulsar-io-5-3] WARN io.streamnative.pulsar.handlers.kop.KafkaTopicManager - Get partition-0 error [Namespace bundle for topic (persistent://public/default/angeltest-partition-0) not served by this instance. Please redo the lookup. Request is denied: namespace=public/default]. 2022-05-25T23:54:24,792+0000 [pulsar-io-5-3] INFO org.apache.pulsar.broker.PulsarService - No ledger offloader configured, using NULL instance 2022-05-25T23:54:24,792+0000 [pulsar-io-5-3] INFO org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl - Opening managed ledger public/default/persistent/angeltest 2022-05-25T23:54:24,794+0000 [bookkeeper-ml-scheduler-OrderedScheduler-7-0] INFO org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl - [public/default/persistent/angeltest] Closing managed ledger 2022-05-25T23:54:24,794+0000 [bookkeeper-ml-scheduler-OrderedScheduler-7-0] ERROR io.streamnative.pulsar.handlers.kop.KafkaTopicManager - [[id: 0x2254288d, L:/10.42.52.172:19092 - R:/10.127.58.41:58628]]Get empty non-partitioned topic for name persistent://public/default/angeltest 2022-05-25T23:54:24,794+0000 [bookkeeper-ml-scheduler-OrderedScheduler-7-0] ERROR io.streamnative.pulsar.handlers.kop.KafkaTopicManager - [[id: 0x2254288d, L:/10.42.52.172:19092 - R:/10.127.58.41:58628]] Failed to getTopicConsumerManager caused by getTopic 'persistent://public/default/angeltest-partition-0' returns empty

Additional context Pulsar version: 2.9.1 KOP VERSION 2.9.2.17

[rillo-carrillo]

Issue has been fix, we used to have one service for all the external connections, now we have one service for each broker for external connections.

[dispalt]

Issue has been fix, we used to have one service for all the external connections, now we have one service for each broker for external connections.

Assuming you installed this with helm, how did you manage that?