Bug #6484
closedosd pool default flag hashpspool not honored
0%
Description
When creating new pools the hashpspool is not honored. And as there's no way to change it aafter pool creation, there's no way to actually activate this flag on any pools.
--
ceph -v
ceph version 0.67.4 (ad85b8bfafea6232d64cb7ba76a8b6e8252fa0c7)
--
ceph.conf
[osd]
osd journal size = 100
filestore xattr use omap = true
auth cluster required = cephx
auth service required = cephx
auth client required = cephx
osd min pg log entries = 1000
osd max pg log entries = 3000
osd pool default flag hashpspool = true
cephx require signatures = true
[mon.a]
host = gt680
mon addr = 127.0.0.1:6789
[osd.0]
host = gt680
[osd.1]
host = gt680
--
ceph osd pool create test1 8
pool 'test1' created
--
ceph osd dump
epoch 584
fsid 7145792b-91fe-48bc-b5cd-e49c4df0ec89
created 2013-08-20 20:40:53.111255
modified 2013-10-08 10:38:57.647026
flags
pool 28 'test1' rep size 2 min_size 1 crush_ruleset 0 object_hash rjenkins pg_num 8 pgp_num 8 last_change 583 owner 0
Updated by Sage Weil over 10 years ago
- Status changed from New to Resolved
it is now possible to add the flag to an existing pool in master. this will be in emperor.
the option works too, but it needs to be set on the monitor (so [mon] or [global]) in order to affect new pools. it's confusing, sorry!
Updated by Corin Langosch over 10 years ago
Ok, after moving the directive to the [mon] section is seems to work. At least the new pool now has the addition "flags 1".
I just created another ticket regarding making ceph emit a warning when unknown/ invalid directives are found in the config file (http://tracker.ceph.com/issues/6567).