My understanding is that Monitors monitor the public address of the OSDs and other OSDs monitor the cluster address of the OSDs. Replication, recovery and backfill traffic all use the same network when you specify 'cluster network = <network/mask>' in your ceph.conf. It is useful to remember that replication, recovery and backfill traffic are pretty much the same thing, just at different points in time. On Sun, Apr 26, 2015 at 4:39 PM, Sebastien Han <sebastien.han@xxxxxxxxxxxx> wrote: > Hi list, > > While reading this http://ceph.com/docs/master/rados/configuration/network-config-ref/#ceph-networks, I came across the following sentence: > > "You can also establish a separate cluster network to handle OSD heartbeat, object replication and recovery traffic” > > I didn’t know it was possible to perform such stretching, at least for recovery traffic. > Replication is generally handled by the cluster_network_addr and the heartbeat can be used with osd_heartbeat_addr. > Although I’m a bit confused by the osd_heartbeat_addr since I thought the heartbeat was binding on both public and cluster addresses. > > So my question is: how to isolate the recovery traffic to specific network? > > Thanks! > > Cheers. > –––– > Sébastien Han > Cloud Architect > > "Always give 100%. Unless you're giving blood." > > Phone: +33 (0)1 49 70 99 72 > Mail: sebastien.han@xxxxxxxxxxxx > Address : 11 bis, rue Roquépine - 75008 Paris > Web : www.enovance.com - Twitter : @enovance > > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |