The client_force_lazyio option is currently marked as supporting
runtime updates in the configuration schema, but this is misleading.
The value is read once during each file open/create and stored in
the file flags. There is no config observer registered to handle
dynamic updates, and there is no logic to propagate changes to the
already opened file handles.
This patch adds the NO_RUNTIME flag to the option definition to
correctly reflect reality.
Fixes: https://tracker.ceph.com/issues/77451
Signed-off-by: Xiubo Li <xiubo.li@clyso.com>
+* CephFS: The ``client_force_lazyio`` configuration option is now correctly marked
+ as not supporting runtime updates. Previously, the configuration schema indicated
+ this option could be changed at runtime, but changes had no effect on opened file
+ handlers in ceph-fuse or libcephfs clients because there is no logic to propagate
+ changes to open file handles.
+
* RADOS: PG autoscaler allows overlapping roots. Each root receives a PG target based
on its OSDs, with OSDs shared across multiple roots contributing proportionally
less to each root's allocation.
LazyIO can be enabled in the following ways.
- ``client_force_lazyio`` option enables LAZY_IO globally for libcephfs and
- ceph-fuse mount.
+ ceph-fuse mount. This is strictly a startup flag.
- ``ceph_lazyio(...)`` and ``ceph_ll_lazyio(...)`` enable LAZY_IO for file handle
in libcephfs.
default: false
services:
- mds_client
+ flags:
+ - startup
- name: fuse_use_invalidate_cb
type: bool
level: advanced