[SERVER-31868] investigate should afterClusterTime be allowed to be specified for standalone mongod Created: 08/Nov/17  Updated: 27/Oct/23  Resolved: 17/Nov/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Misha Tyulenev
Resolution: Works as Designed Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-43463 Complete TODO listed in SERVER-31868 Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-11-13, Sharding 2017-12-04
Participants:

 Description   

investigate if returning an error is better then ignoring when afterClusterTime is specified for standalone mongod.

https://github.com/mongodb/mongo/blob/master/src/mongo/db/read_concern.cpp#L188
confirm that a user can not trigger this invariant by passing afterClusterTime.



 Comments   
Comment by Misha Tyulenev [ 17/Nov/17 ]

This will be rejected in https://github.com/mongodb/mongo/blob/v3.6/src/mongo/db/repl/replication_coordinator_impl.cpp#L1179

Comment by Max Hirschhorn [ 08/Nov/17 ]

misha.tyulenev, my understanding of SERVER-28812 is that you had wanted specifying "afterClusterTime" to a stand-alone mongod to still succeed, i.e. to not return an error.

Generated at Thu Feb 08 04:28:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.