The flag is fine, it's just to ensure that OSDs from a release before Jewel can't be added to the cluster:
See http://ceph.com/geen-categorie/v10-2-4-jewel-released/ under "Upgrading from hammer"
On Thu, 13 Jul 2017 at 07:59 Jan Krcmar <honza801@xxxxxxxxx> wrote:
hi,
is it possible to remove the require_jewel_osds flag after upgrade to kraken?
$ ceph osd stat
osdmap e29021: 40 osds: 40 up, 40 in
flags sortbitwise,require_jewel_osds,require_kraken_osds
it seems that ceph osd unset does not support require_jewel_osds
$ ceph osd unset require_jewel_osds
Invalid command: require_jewel_osds not in
full|pause|noup|nodown|noout|noin|nobackfill|norebalance|norecover|noscrub|nodeep-scrub|notieragent|sortbitwise
osd unset full|pause|noup|nodown|noout|noin|nobackfill|norebalance|norecover|noscrub|nodeep-scrub|notieragent|sortbitwise
: unset <key>
Error EINVAL: invalid command
is there any way to remove it?
if not, is it ok to leave the flag there?
thanks
fous
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com