Bug 2246799 - [GSS][DOC] Document default ReclaimSpace interval @weekly may introduce performance degradation.
Summary: [GSS][DOC] Document default ReclaimSpace interval @weekly may introduce perfo...
Keywords:
Status: ON_QA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: documentation
Version: 4.13
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ---
: ---
Assignee: Erin Donnelly
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-10-29 02:53 UTC by Kenichiro Kagoshima
Modified: 2024-04-09 17:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Kenichiro Kagoshima 2023-10-29 02:53:32 UTC
Describe the issue:
Following note has added with ODF 4.13. 
-------------------------------
"Recommended schedule interval is @weekly. If the schedule interval value is empty or in an invalid format, then the default schedule value is set to @weekly. "
-------------------------------
As we know, the ReclaimSpace operation introduces performance penalty. And we're asking schedule the ReclaimSpace operation during off-peak, maintenance window, or the interval when the workload
input/output is expected to be low.
We also need to document not schedule multiple ReclaimSpace @weekly or at a same time to avoid
the heavy workload.

Describe the task you were trying to accomplish:

Suggestions for improvement:

Document URL:
https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.13/html-single/managing_and_allocating_storage_resources/index#enabling-reclaim-space-operation-using-annotating-persistentvolumeclaims_rhodf

Chapter/Section Number and Title:
Chapter 10. Reclaiming space on target volumes
10.1. Enabling reclaim space operation using Annotating PersistentVolumeClaims
Note:

Product Version:
4.13

Environment Details:

Any other versions of this document that also needs this update:

Additional information:


Note You need to log in before you can comment on or make changes to this bug.