we have a use case where requires send message across multiple data centers . A through B to C。 #18856
Replies: 4 comments
-
the messages replicated from cluster1 to cluster2 are marked as "replicated message", these message will not replicate again to cluster3. |
Beta Was this translation helpful? Give feedback.
-
@fengxiaokai In the above case you provided, you should also add cluster-3 for the namespace in cluster-1 |
Beta Was this translation helpful? Give feedback.
-
The issue had no activity for 30 days, mark with Stale label. |
Beta Was this translation helpful? Give feedback.
-
The issue had no activity for 30 days, mark with Stale label. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
we have a use case where requires send message across multiple data centers . A through B to C. C cannot consume messages.
To Reproduce
Steps to reproduce the behavior:
create cluster2
bin/pulsar-admin clusters create
--broker-url pulsar://172.23.80.1:6652
--url http://172.23.80.1:8082
cluster2
create tenant
bin/pulsar-admin tenants create my-tenant
--admin-roles my-admin-role
--allowed-clusters cluster1,cluster2
create namespace
bin/pulsar-admin namespaces create my-tenant/my-namespace
set geo-replication
bin/pulsar-admin namespaces set-clusters my-tenant/my-namespace --clusters cluster1,cluster2
create topics
bin/pulsar-admin topics create persistent://my-tenant/my-namespace/my-topic3
2. cluster2
create cluster3
bin/pulsar-admin clusters create
--broker-url pulsar://172.23.80.1:6653
--url http://172.23.80.1:8083
cluster3
create tenant
bin/pulsar-admin tenants create my-tenant
--admin-roles my-admin-role
--allowed-clusters cluster2,cluster3
create namespace
bin/pulsar-admin namespaces create my-tenant/my-namespace
set namespace geo-replication
bin/pulsar-admin namespaces set-clusters my-tenant/my-namespace --clusters cluster2,cluster3
create tenant
bin/pulsar-admin tenants create my-tenant
--admin-roles my-admin-role
--allowed-clusters cluster3
create namespace
bin/pulsar-admin namespaces create my-tenant/my-namespace
bin/pulsar-client produce persistent://my-tenant/my-namespace/my-topic3 -m “message1”
bin/pulsar-client consume persistent://my-tenant/my-namespace/my-topic3 -n 0 -s consume2
6.cluster3 cannot consume messages
bin/pulsar-client consume persistent://my-tenant/my-namespace/my-topic3 -n 0 -s consume3
Expected behavior
cluster3 can consume messages
Beta Was this translation helpful? Give feedback.
All reactions