Project

General

Profile

Actions

Documentation #15444

closed

orphan cleanup tool: document/test interaction w/ placement targets & multiple data pools

Added by Robin Johnson about 8 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Tags:
rgw, orphan
Backport:
hammer
Reviewed:
Affected Versions:
Pull request ID:

Description

The Orphan tool documentation should cover how to handle environments with multiple data pools.

Consider the setup from https://blog-fromsomedude.rhcloud.com/2015/11/06/Ceph-RadosGW-Placement-Targets/:

{
    "domain_root": ".rgw",
    "control_pool": ".rgw.control",
    "gc_pool": ".rgw.gc",
    "log_pool": ".log",
    "intent_log_pool": ".intent-log",
    "usage_log_pool": ".usage",
    "user_keys_pool": ".users",
    "user_email_pool": ".users.email",
    "user_swift_pool": ".users.swift",
    "user_uid_pool": ".users.uid",
    "system_key": {
        "access_key": "",
        "secret_key": "" 
    },
    "placement_pools": [
        {
            "key": "default-placement",
            "val": {
                "index_pool": ".rgw.buckets.index",
                "data_pool": ".rgw.buckets",
                "data_extra_pool": ".rgw.buckets.extra" 
            }
        },
        {
            "key": "ssd",
            "val": {
                "index_pool": ".rgw.buckets-ssd.index",
                "data_pool": ".rgw.buckets-ssd",
                "data_extra_pool": ".rgw.buckets-ssd.extra" 
            }

        },
    ]
}

Should this be a two runs of orphan-find? What about when the index pool and/or extra pools are shared, with just the data pool separate?

Actions #1

Updated by Loïc Dachary over 7 years ago

  • Backport changed from hammer, infernalis to hammer

infernalis is EOL

Actions #2

Updated by Zac Dover over 4 years ago

  • Status changed from New to Closed

This bug has been judged too old to fix. This is because either it is either 1) raised against a version of Ceph prior to Luminous, or 2) just really old, and untouched for so long that it is unlikely nowadays to represent a live documentation concern.

If you think that the closing of this bug is an error, raise another bug of a similar kind. If you think that the matter requires urgent attention, please let Zac Dover know at .

Actions

Also available in: Atom PDF