Chaunceyan opened a new issue #14266: URL: https://github.com/apache/pulsar/issues/14266
**Describe the bug** I am using geo-replication on namespace level with version 2.8.1. Some time ago we changed the DNS record so the geo-replication failed. But there were already some topics created. When I try to update the geo-replication config with the following command: _bin/pulsar-admin clusters update ..._ _bin/pulsar-admin namespaces set-clusters_ The replication process does not recover as expected. I noticed in the log that the replicator still tries to connect to the outdated cluster URL.  While I managed to solve this by find the relevant broker and restart it, It seems there is some issue with config cache update? **To Reproduce** Well I definitely failed to reproduce this, after broker restart, they could sync the update just fine. Probably try first with a failed replication config and then update with the right info. **Expected behavior** Expect the change of replication clusters URL taken effect without need for server restart **Screenshots**  **Desktop (please complete the following information):** - OS: [e.g. iOS] - centOS **Additional context** Add any other context about the problem here. -- 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]
