mismatch between min-compat-client and connected clients

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




hello

in a cluster running octopus, i've set the upmap balancer; in order to
do so i had to set the set-require-min-compat-client flag to luminous

however i can still mount my cephfs exports using old kernels (3.10.0-1160.el7)
and more surprisingly clients appear in ceph features as jewel clients

$ ceph osd get-require-min-compat-client
luminous

$ ceph features
...
    "features": "0x27018fb86aa42ada",
    "release": "jewel",
    "num": 1

how is this possible? shouldn't the mount request fail if the
min-compat-client is not satisfied?

the client can use the fs just fine, the balancer hasn't been active
yet since the cluster is still remapping pgs from previous manual
changes (skips because too many objects displaced) Would that cause the
issue? will the old client break when the upmap balancer runs?

PS: i cannot set the min-compat-client to luminous if old clients are
connected

thanks
--
IRC: gfa
GPG: 0x27263FA42553615F904A7EBE2A40A2ECB8DAD8D5
OLD GPG: 0x44BB1BA79F6C6333
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux