You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "Chaunceyan (via GitHub)" <gi...@apache.org> on 2023/06/29 09:51:01 UTC

[GitHub] [pulsar] Chaunceyan created a discussion: Manual Failover on replicated clusters

GitHub user Chaunceyan created a discussion: Manual Failover on replicated clusters

Dear Community, 

We have clusters A and B. They are replications of each other, subscriptions include.

At first our clients were connecting to cluster A through a hostname, say "pulsar.local". We then changed the DNS pointing pulsar.local to cluster B, nothing happens.

The clients are still connecting to cluster A broker in direct IP connection. We have to manually reboot the clients for the DNS change to take effect. 

I wonder if there is better option, like server side operation, to trigger the clients to create new connection. 
Will unloading namespace do the trick?

GitHub link: https://github.com/apache/pulsar/discussions/20681

----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org