Ceph RGW - Garbage Collection(GC) Tuning options

Solution Verified - Updated

Environment

  • Red Hat Ceph Storage 3.2 and above

Issue

  • Ceph RGW - Garbage Collection(GC) Tuning options

Resolution

  • rgw_gc_max_objs: Number of shards for garbage collector data
    Default value: 32
    Description: The number of garbage collector data shards is the number of RADOS objects that RGW will use to store the garbage collection information on. NOTE: this count cannot be set dynamically and should not be changed after inital creation. Do NOT change this value unless Red Hat Support is engaged and the environement is not currently servicing RGW workloads

  • rgw_gc_obj_min_wait: Garabge collection object expiration time
    Default value: 7200 seconds
    Description: The length of time (in seconds) that the RGW collector will wait before purging a deleted object's data. RGW will not remove object immediately, as the object could still have readers. A mechanism exists to increase the object's expiration time when it's being read.

  • rgw_gc_processor_max_time: Length of time GC processor can lease shard
    Default value: 3600 seconds
    Description: Garbage collection thread in RGW process holds a lease on its data shards. These objects contain information about the objects that need to be removed. RGW takes a lease in order to prevent multiple RGW processes from handling the same objects concurrently. This time signifies that maximum amount of time that RGW is allowed to hold that lease. In the case where RGW goes down uncleanly, this is the amount of time where processing of that data shard will be blocked.

  • rgw_gc_processor_period: Garbage collector cycle run time
    Default value: 3600 seconds
    Description: The amount of time between the start of consecutive runs of the garbage collector threads. If garbage collector runs takes more than this period, it will not wait before running again.

  • rgw_gc_max_concurrent_io: Max concurrent RADOS IO operations for garbage collection
    Default value: 10
    Description: The maximum number of concurrent IO operations that the RGW garbage collection thread will use when purging old data.

  • rgw_gc_max_trim_chunk: Max number of keys to remove from garbage collector log in a single operation.
    Default value: 16
    Description: Max number of keys to remove from garbage collector log in a single operation.

SBR
Product(s)
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.