On Wed, Dec 20, 2017 at 6:56 PM, Jason Dillaman <jdillama@xxxxxxxxxx> wrote: > ... looks like this watch "timeout" was introduced in the kraken > release [1] so if you don't see this issue with a Jewel cluster, I > suspect that's the cause. > > [1] https://github.com/ceph/ceph/pull/11378 Strictly speaking that's a backwards incompatible change, because zeroes have never been and aren't enforced -- clients are free to fill the remaining bits of ceph_osd_op with whatever values. That said, the kernel client has always been zeroing the front portion of the message before encoding, so even though the timeout field hasn't been carried into ceph_osd_op definition in the kernel, it's always 0 (for "use osd_client_watch_timeout for this watch"). Thanks, Ilya _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |