diff options
author | Yuval Lifshitz <ylifshit@ibm.com> | 2024-12-24 19:22:58 +0100 |
---|---|---|
committer | Yuval Lifshitz <ylifshit@ibm.com> | 2025-01-13 07:38:49 +0100 |
commit | fcfc50b2313692398edfe192f885d4e58a54c657 (patch) | |
tree | 28c8a39e7527764e4bc8e0cbfdc986667ff8e4d8 /doc | |
parent | rgw/logging: retry attribuite set in case of race (diff) | |
download | ceph-fcfc50b2313692398edfe192f885d4e58a54c657.tar.xz ceph-fcfc50b2313692398edfe192f885d4e58a54c657.zip |
rgw/logging: clean pending objects
* when source bucket is deleted
* when logging is disabled
* when logging conf changes
* when target bucket is deleted
also add "bucket logging info" admin command
returning logging conf for source bucket, and list
of source buckets for log bucket
Signed-off-by: Yuval Lifshitz <ylifshit@ibm.com>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/radosgw/bucket_logging.rst | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/radosgw/bucket_logging.rst b/doc/radosgw/bucket_logging.rst index df469497383..f3e790f5705 100644 --- a/doc/radosgw/bucket_logging.rst +++ b/doc/radosgw/bucket_logging.rst @@ -35,6 +35,7 @@ Adding a log object to the log bucket is done "lazily", meaning, that if no more remain outside of the log bucket even after the configured time has passed. To counter that, you can flush all logging objects on a given source bucket to log them, regardless if enough time passed or if no more records are written to the object. +Flushing will happen automatically when logging is disabled on a bucket, its logging configuration is changed, or the bucket is deleted. Standard ```````` |