Hi, cluster_network and public_network are read when a daemon starts up in order to decide which interface to bind to, and which IP address / port to advertise to the rest of the cluster. So you can normally modify any of those, as long as all the daemons can still reach each other on the new IPs. What I suggest is that you should test it on one daemon first, so you confirm that it works. Suppose you have right now: global public_network <A> global cluster_network <B> Then pick any osd to test, like osd.0 1. ceph config set osd.0 cluster_network <A> # set the cluster network to the same as public, for osd.0 only. 2. Restart osd.0 3. ceph osd dump | grep osd.0 # check that the backend addr is now the same network as the frontend. (Backend == cluster, frontend == public). 4. Assuming it all worked, then you can try a few more, e.g. try one mon, one mds, etc... 5. Assuming it is all working, then do something like ceph config rm osd.0 cluster_network # to inherit the global setting ceph config rm global cluster_network # to remove the global. now everything will use just public_network .. restart all the daemons, gracefully according to failure domains etc. Cheers, Dan On Thu, Jan 9, 2025 at 6:08 PM 苏察哈尔灿 <2644294460@qq.com> wrote:
Hello, I have installed a ceph cluster, version v17.2.8, the cluster has public_network and cluster_network. For some other reason, I want to temporarily remove cluster_network and let the service data, heartbeat detection, and data recovery be done on public_network. Is this achievable? After removing it, if you want to configure it back, can you also achieve it?
Thank you! _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
-- Dan van der Ster CTO @ CLYSO Try our Ceph Analyzer -- https://analyzer.clyso.com/ https://clyso.com | dan.vanderster@clyso.com