lordcheng10 opened a new issue #12138: URL: https://github.com/apache/pulsar/issues/12138
**Describe the bug** After the replication subscription is turned on, changing cluster consumption does not continue to consume **To Reproduce** Steps to reproduce the behavior: 1. Create a tenant: bin/pulsar-admin tenants create my-tenant3 --admin-roles my-admin-role --allowed-clusters ss_share1,ss_share2 2. Create a namespace: bin/pulsar-admin namespaces create my-tenant3/my-namespace bin/pulsar-admin namespaces set-clusters my-tenant3/my-namespace --clusters ss_share1,ss_share2 3. Create topic and subscription: ./bin/pulsar-admin topics create-partitioned-topic my-tenant3/my-namespace/test1 --partitions 1 sh bin/pulsar-admin --admin-url http://localhost:8083 topics create-subscription my-tenant3/my-namespace/test1 -s sub1 4. Turn on copy subscription: sh bin/pulsar-admin topics set-replicated-subscription-status -e -s sub1 persistent://my-tenant3/my-namespace/test1 5. In the ss_share1 cluster, write messages 1, 2, and 3: bin/pulsar-client produce my-tenant3/my-namespace/test1 --messages 1 bin/pulsar-client produce my-tenant3/my-namespace/test1 --messages 2 bin/pulsar-client produce my-tenant3/my-namespace/test1 --messages 3 6. Consume messages 1, 2, and 3 in the ss_share1 cluster: ./bin/pulsar-client consume my-tenant3/my-namespace/test1 -p Earliest -s sub1 -n 3 7. In the ss_share1 cluster, write messages 4, 5, 6; 8. Consumption of messages in the ss_share2 cluster: ./bin/pulsar-client consume my-tenant3/my-namespace/test1 -p Earliest -s sub1 -n 3 **Expected behavior** The last message consumed should be 4, 5, 6. But it’s actually 1, 2, 3 -- 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]
