Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mimic: doc: Minor rados related documentation fixes #27188

Merged
merged 1 commit into from Apr 12, 2019
Merged
Changes from all commits
Commits
File filter...
Filter file types
Jump to…
Jump to file or symbol
Failed to load files and symbols.

Always

Just for now

@@ -97,8 +97,11 @@ User-visible PG States
*down*
a replica with necessary data is down, so the pg is offline

*replay*
the PG is waiting for clients to replay operations after an OSD crashed
*recovery_unfound*
recovery could not finish because object(s) are unfound.

*backfill_unfound*
backfill could not finish because object(s) are unfound.

*splitting*
the PG is being split into multiple PGs (not functional as of 2012-02)
@@ -123,20 +126,9 @@ User-visible PG States
*recovering*
objects are being migrated/synchronized with replicas

*recovery_wait*
the PG is waiting for the local/remote recovery reservations

*backfilling*
a special case of recovery, in which the entire contents of
the PG are scanned and synchronized, instead of inferring what
needs to be transferred from the PG logs of recent operations

*backfill_wait*
the PG is waiting in line to start backfill

*backfill_toofull*
backfill reservation rejected, OSD too full

*incomplete*
a pg is missing a necessary period of history from its
log. If you see this state, report a bug, and try to start any
@@ -149,3 +141,44 @@ User-visible PG States
*remapped*
the PG is temporarily mapped to a different set of OSDs from what
CRUSH specified

*deep*
In conjunction with *scrubbing* the scrub is a deep scrub

*backfilling*
a special case of recovery, in which the entire contents of
the PG are scanned and synchronized, instead of inferring what
needs to be transferred from the PG logs of recent operations

*backfill_toofull*
backfill reservation rejected, OSD too full

*recovery_wait*
the PG is waiting for the local/remote recovery reservations

*undersized*
the PG can't select enough OSDs given its size

*activating*
the PG is peered but not yet active

*peered*
the PG peered but can't go active

*snaptrim*
the PG is trimming snaps

*snaptrim_wait*
the PG is queued to trim snaps

*recovery_toofull*
recovery reservation rejected, OSD too full

*snaptrim_error*
the PG could not complete snap trimming due to errors

*forced_recovery*
the PG has been marked for highest priority recovery

*forced_backfill*
the PG has been marked for highest priority backfill
@@ -342,6 +342,22 @@ scrubbing operations.
:Default: 512 KB. ``524288``


``osd scrub auto repair``

:Description: Setting this to ``true`` will enable automatic pg repair when errors
are found in deep-scrub. However, if more than ``osd scrub auto repair num errors``
errors are found a repair is NOT performed.
:Type: Boolean
:Default: ``false``


``osd scrub auto repair num errors``

:Description: Auto repair will not occur if more than this many errors are found.
:Type: 32-bit Integer
:Default: ``5``


.. index:: OSD; operations settings

Operations
ProTip! Use n and p to navigate between commits in a pull request.
You can’t perform that action at this time.