[DOCS-7498] clarify $currentDate behavior does not assure monotonic sequence Created: 24/Mar/16 Updated: 30/Oct/23 Resolved: 09/Apr/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Ryder (Inactive) | Assignee: | Steve Renaker (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 47 weeks ago | ||||||||
| Description |
|
RE: https://docs.mongodb.org/manual/reference/operator/update/currentDate/ $currentDate does not provide any assurance that consecutive updates will show an increasing (or even static) value. It is possible for an external client to perform consecutive reads where a field being updated using $currentDate is observed to go backwards. This effect can theoretically occur on a standalone server without any changes to the system clock. Although the opportunity for the effect increases with a replica-set (elections) or system clock changes. |