Skip to content

DOCS-14122-compact-clarification #5641

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jul 29, 2021
Merged

DOCS-14122-compact-clarification #5641

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 1 addition & 5 deletions source/reference/command/compact.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,11 +226,7 @@ Replica Sets
- Ideally run :dbcommand:`compact` on a secondary. See option
``force`` above for information regarding compacting the primary.

Before v4.4, :dbcommand:`compact` forced the secondary to enter
:replstate:`RECOVERING` state during its execution, which caused read
operations from clients to fail. Starting in v4.4, :dbcommand:`compact`
does not change the run state of the secondary, and clients may continue
to read from the secondary during the compaction operation.
.. include:: /includes/extracts/fact-command-puts-secondary-into-recovering-compact.rst

Sharded Clusters
~~~~~~~~~~~~~~~~
Expand Down