Hi,
without having checked the tracker, does anyone have an explanation
why the size parameter is not applied when creating a pool via CLI?
According to the help output for 'ceph osd pool create -h' you can
specify expected_num_objects (btw. I don't understand what impact that
has, all I could find was related to filestore OSDs and PG splitting)
and then the size:
profile>] [<rule>] [<expected_num_objects:int>] [<size:int>]
[<pg_num_min:int>] [<pg_num_max:
If I specify both parameters, the pool gets its default size according
to osd_pool_default_size (this is a single node cluster, hence default
size 2):
soc9-ceph:~ # ceph osd pool create temp5 4 replicated replicated_rule 0 4
pool 4 'temp5' replicated size 2 min_size 1 crush_rule 0 object_hash
rjenkins pg_num 4 pgp_num 4 autoscale_mode off last_change 260 flags
hashpspool stripe_width 0 read_balance_score 1.00
I get the same result on a larger test cluster with multiple hosts. Of
course I know that I could just set the size afterwards, but is the
command broken? Has anyone looked into this?
Thanks!
Eugen
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
