eolivelli opened a new issue #12727: URL: https://github.com/apache/pulsar/issues/12727
**Describe the bug** In my application I see that Pulsar is creating many topics, appending "_transaction_pending_ack-__pending_ack_state__transaction_pending_ack" to the previous topic name. for instance if I create a Reader for "MY_TOPIC" I see this... `persistent://public/default/MY_TOPIC-8975a6f5-be96-4c03-b5b9-02ad570dd1f9__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack-__pending_ack_state__transaction_pending_ack` Each topic has one subscription '__pending_ack_state' **To Reproduce** Create a Consumer with Transactions and EnableAckReceipt, use it **Expected behavior** Only at topic should be created ** Context Pulsar version 2.8.1 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
