Skip to content

(DOCSP-6257): Fixing inaccurate description of delete timing for TTL … #3853

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
Jan 10, 2020
Merged

(DOCSP-6257): Fixing inaccurate description of delete timing for TTL … #3853

Show file tree
Hide file tree
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
4 changes: 3 additions & 1 deletion source/core/index-ttl.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,9 @@ output of :method:`db.currentOp()` or in the data collected by the
Timing of the Delete Operation
``````````````````````````````

.. include:: /includes/extracts/4.2-index-ttl.rst
MongoDB begins removing expired documents as soon as the index
finishes building on the :term:`primary`. For more information on the
index build process, see :ref:`index-operations`.

.. include:: /includes/fact-ttl-collection-background-timing.rst

Expand Down
22 changes: 1 addition & 21 deletions source/includes/extracts-hybrid-index-fcv.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,26 +15,6 @@ content: |
lock only at the beginning and end of the build process. The rest of
the build process yields to interleaving read and write operations.
MongoDB ignores the ``background`` option if specified.

---
ref: 4.2-index-ttl
content: |

For :ref:`feature compatibility version (fcv) <view-fcv>` ``"4.2"``,
MongoDB begins removing expired documents as soon as the
index finishes building.

For :ref:`feature compatibility version (fcv) <view-fcv>` ``"4.0"``,
the timing of delete operations depends on the index build type:

- With foreground index builds, MongoDB can begin removing
expired documents only *after* the build completes.

- With background index builds, MongoDB can begin removing
expired documents as soon as the they are processed by the build.

For more information on the index build process, see
:ref:`index-operations`.
---
ref: 4.2-rollbacks
content: |
Expand Down Expand Up @@ -82,4 +62,4 @@ content: |
- For :ref:`feature compatibility version (fcv) <view-fcv>` ``"4.0"``,
the index build memory limit only applies to foreground
index builds.
...
...