From 242ef7824dade914d17b6b367f0430c0df448ca0 Mon Sep 17 00:00:00 2001 From: Sage Weil Date: Tue, 2 Apr 2019 09:19:04 -0500 Subject: [PATCH] doc/rados/operations: document BLUEFS_SPILLOVER Signed-off-by: Sage Weil --- doc/rados/operations/health-checks.rst | 28 ++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/doc/rados/operations/health-checks.rst b/doc/rados/operations/health-checks.rst index 09b748eabe3..60c9df62176 100644 --- a/doc/rados/operations/health-checks.rst +++ b/doc/rados/operations/health-checks.rst @@ -301,6 +301,34 @@ You can either raise the pool quota with:: or delete some existing data to reduce utilization. +BLUEFS_SPILLOVER +________________ + +One or more OSDs that use the BlueStore backend have been allocated +`db` partitions (storage space for metadata, normally on a faster +device) but that space has filled, such that metadata has "spilled +over" onto the normal slow device. This isn't necessarily an error +condition or even unexpected, but if the administrator's expectation +was that all metadata would fit on the faster device, it indicates +that not enough space was provided. + +This warning can be disabled on all OSDs with:: + + ceph config set osd bluestore_warn_on_bluefs_spillover false + +Alternatively, it can be disabled on a specific OSD with:: + + ceph config set osd.123 bluestore_warn_on_bluefs_spillover false + +To provide more metadata space, the OSD in question could be destroyed and +reprovisioned. This will involve data migration and recovery. + +It may also be possible to expand the LVM logical volume backing the +`db` storage. If the underlying LV has been expanded, the OSD daemon +needs to be stopped and BlueFS informed of the device size change with:: + + ceph-bluestore-tool bluefs-bdev-expand --path /var/lib/ceph/osd/ceph-$ID + Device health ------------- -- 2.39.5