[DOCS-14225] Production notes incorrectly suggest TTL deletes on secondaries rely on clock Created: 12/Feb/21  Updated: 30/Oct/23  Due: 26/Feb/21  Resolved: 17/Feb/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: Asya Kamsky Assignee: Andrew Feierabend (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 2 years, 51 weeks, 5 days ago
Epic Link: DOCSP-11701
Story Points: 2

 Description   

Description

See https://github.com/mongodb/docs/pull/4754 for fix - the "for example" paragraph is incorrect and should be removed.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Asya Kamsky [ 12/Feb/21 ]

Technically, that paragraph could be kept if we changed "member" to "shard" but as it's written it's caused multiple people to assume that replica set node clocks being out of sync can mess up TTL process.

Generated at Thu Feb 08 08:09:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.