On 11/17/23 00:41, Ilya Dryomov wrote:
On Thu, Nov 16, 2023 at 5:26 PM Matt Larson <larsonmattr@gmail.com> wrote:
Ilya,
Thank you for providing these discussion threads on the Kernel fixes for where there was a change and details on this affects the clients.
What is the expected behavior in CephFS client when there are multiple data pools in the CephFS? Does having 'nearfull' in any data pool in the CephFS then trigger the synchronous writes for clients even if they would be writing to a CephFS location mapped to a non-nearfull data pool? I.e. is 'nearfull' / sync behavior global across the same CephFS filesystem? I would expect it to apply only to the pool in question (i.e. not be global), but let's get Xiubo or someone else working on CephFS to confirm.
It seems just before mimic when any pool is nearfull it will affect the whole cephfs, and after since mimic the 'CEPH_OSDMAP_NEARFULL' has been deprecated, so it will depends on each pool. -#define CEPH_OSDMAP_NEARFULL (1<<0) /* sync writes (near ENOSPC) */ -#define CEPH_OSDMAP_FULL (1<<1) /* no data writes (ENOSPC) */ +#define CEPH_OSDMAP_NEARFULL (1<<0) /* sync writes (near ENOSPC), deprecated since mimic*/ +#define CEPH_OSDMAP_FULL (1<<1) /* no data writes (ENOSPC), deprecated since mimic */ Thanks - Xiubo
Thanks,
Ilya