--
> *From:* Oliver Freyermuth
> *Sent:* Friday, 26 October 2018 9:32:14 PM
> *To:* Linh Vu; Janne Johansson
> *Cc:* ceph-users@lists.ceph.com; Peter Wienemann
-------------------------
upmap has been amazing and balanced my clusters far better than anything
else I've ever seen. I would go so far as to say that upmap can achieve a
perfect balance.
Upmap is awesome. I ran it on our new cluster before we started ingesting data,
so that the PG count is balanced on all OSDs.
G
I haven't had crush-compat do anything helpful for balancing my clusters.
upmap has been amazing and balanced my clusters far better than anything
else I've ever seen. I would go so far as to say that upmap can achieve a
perfect balance.
It seems to evenly distribute the PGs for each pool onto al
Ok, I'll try out the balancer end of the upcoming week then (after we've fixed
a HW-issue with one of our mons
and the cooling system).
Until then, any further advice and whether upmap is recommended over
crush-compat (all clients are Luminous) are welcome ;-).
Cheers,
Oliver
Am 20.10.18 um
All OSDs are of the very same size. One OSD host has slightly more disks (33
instead of 31), though.
So also that that can't explain the hefty difference.
I attach the output of "ceph osd tree" and "ceph osd df".
The crush rule for the ceph_data pool is:
rule cephfs_data {
id 2
Yes, if you have uneven sizes I guess you could end up in a situation
where you have
lots of 1TB OSDs and a number of 2TB OSD but pool replication forces
the pool to have one
PG replica on the 1TB OSD, then it would be possible to state "this
pool cant write more than X G"
but when it is full, ther
Dear Janne,
yes, of course. But since we only have two pools here, this can not explain the
difference.
The metadata is replicated (3 copies) across ssd drives, and we have < 3 TB of
total raw storage for that.
So looking at the raw space usage, we can ignore that.
All the rest is used for t
Do mind that drives may have more than one pool on them, so RAW space
is what it says, how much free space there is. Then the avail and
%USED on per-pool stats will take replication into account, it can
tell how much data you may write into that particular pool, given that
pools replication or EC s
Dear Cephalopodians,
as many others, I'm also a bit confused by "ceph df" output
in a pretty straightforward configuration.
We have a CephFS (12.2.7) running, with 4+2 EC profile.
I get:
# ceph df
GLOBAL:
SIZE
10 matches
Mail list logo
