Re: [ceph-users] mon not binding to public interface

2014-01-15 Thread John Wilkins
Monitors use the public network, not the cluster network. Only OSDs use the cluster network. The purpose of the cluster network is that OSDs do a lot of heartbeat checks, data replication, recovery, and rebalancing. So the cluster network will see more traffic than the front end public network. See

Re: [ceph-users] mon not binding to public interface

2014-01-15 Thread Jeff Bachtel
If I understand correctly then, I should either not specify mon addr or set it to an external IP? Thanks for the clarification, Jeff On 01/15/2014 03:58 PM, John Wilkins wrote: Jeff, First, if you've specified the public and cluster networks in [global], you don't need to specify it anywher

Re: [ceph-users] mon not binding to public interface

2014-01-15 Thread John Wilkins
Jeff, First, if you've specified the public and cluster networks in [global], you don't need to specify it anywhere else. If you do, they get overridden. That's not the issue here. It appears from your ceph.conf file that you've specified an address on the cluster network. Specifically, you specif

[ceph-users] mon not binding to public interface

2014-01-13 Thread Jeff Bachtel
I've got a cluster with 3 mons, all of which are binding solely to a cluster network IP, and neither to 0.0.0.0:6789 nor a public IP. I hadn't noticed the problem until now because it makes little difference in how I normally use Ceph (rbd and radosgw), but now that I'm trying to use cephfs it'