The cluster/private network is only used by the OSDs. Nothing else in ceph
or its clients communicate using it. Everything other than osd to osd
communication uses the public network. That includes the MONs, MDSs,
clients, and anything other than an osd talking to an osd. Nothing else
other than
I looked at one of my test clusters running Jewel on Ubuntu 16.04, and
interestingly I found this(below) in one of the OSD logs, which is different
from your OSD boot log, where none of the compression algorithms seem to be
supported. This hints more at how rocksdb was built on CentOS for Ceph.
All Ceph clients will always first connect to the mons. Mons provide
further information on the cluster such as the IPs of MDS and OSDs.
This means you need to provide the mon IPs to the mount command, not
the MDS IPs. Your first command works by coincidence since
you seem to run the mons and
Hello all,
I am testing the cephFS cluster so that clients could mount -t ceph.
the cluster has 6 nodes, 3 mons (also mds), and 3 osds.
All these 6 nodes has 2 nic, one 1Gb nic with real ip (140.109.0.0) and 1
10Gb nic with virtual ip (10.32.0.0)
140.109. Nic1 1G<-MDS1->Nic2 10G 10.32.
How do I delete an RGW/S3 bucket and its contents if the usual S3 API commands
don't work?
The bucket has S3 delete markers that S3 API commands are not able to remove,
and I'd like to reuse the bucket name. It was set up for versioning and
lifecycles under ceph 12.2.5 which broke the bucket
