From 17d6a993fc17d533460c5f40f3908c708e057c18 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Thu, 23 May 2024 18:45:17 +0200 Subject: Merging upstream version 18.2.3. Signed-off-by: Daniel Baumann --- src/common/options/rgw.yaml.in | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'src/common/options/rgw.yaml.in') diff --git a/src/common/options/rgw.yaml.in b/src/common/options/rgw.yaml.in index 241632a22..9c7f91f9e 100644 --- a/src/common/options/rgw.yaml.in +++ b/src/common/options/rgw.yaml.in @@ -233,7 +233,7 @@ options: long_desc: The lifecycle maintenance thread is responsible for lifecycle related maintenance work. The thread itself can be disabled, but in order for lifecycle to work correctly, at least one RGW in each zone needs to have this thread running. - Havingthe thread enabled on multiple RGW processes within the same zone can spread + Having the thread enabled on multiple RGW processes within the same zone can spread some of the maintenance work between them. default: true services: @@ -359,7 +359,11 @@ options: type: str level: advanced desc: Lifecycle allowed work time - long_desc: Local time window in which the lifecycle maintenance thread can work. + long_desc: Local time window in which the lifecycle maintenance thread can work. It expects + 24-hour time notation. For example, "00:00-23:59" means starting at midnight lifecycle + is allowed to run for the whole day (24 hours). When lifecycle completes, it waits for the + next maintenance window. In this example, if it completes at 01:00, it will resume processing + 23 hours later at the following midnight. default: 00:00-06:00 services: - rgw -- cgit v1.2.3