Skip to content

Remove incorrect TTL reference #4938

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
Feb 17, 2021
Merged

Remove incorrect TTL reference #4938

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
8 changes: 0 additions & 8 deletions source/administration/production-notes.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -659,14 +659,6 @@ operations like the following:
- Features which rely on timekeeping may have inconsistent or
unpredictable behavior in clusters with clock drift between MongoDB
components.

For example, :ref:`TTL indexes <index-feature-ttl>` rely
on the system clock to calculate when to delete a given document. If
two members have different system clock times, each member could
delete a given document covered by the TTL index at a different
time. Since :ref:`sessions` use TTL indexes to control their
lifespan, clock drift could result in inconsistent or unpredictable
session timeout behavior.

NTP synchronization is required for deployments running MongoDB lower
than ``3.4.6`` or ``3.2.17`` with the Wired Tiger storage engine, where
Expand Down