[SERVER-31743] Identify all commands that can not accept afterClusterTime Created: 27/Oct/17  Updated: 27/Oct/23  Resolved: 04/May/18

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

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-31613 Commands that don't currently take an... Closed
Assigned Teams:
Sharding
Sprint: Sharding 2017-12-18
Participants:

 Description   

Per SERVER-31613 some commands return ErrorCodes::InvalidOptions from waitForReadConcern() when an afterClusterTime is specified.

This task is to identify all commands that have this requirement.



 Comments   
Comment by Kaloian Manassiev [ 04/May/18 ]

This ticket was open as a placeholder to proactively identify any commands which should not accept afterClusterTime for various reasons.

The most important ones are replSetGetStatus/replSetHeartbeat/isMaster because they must never block and those have been confirmed to not accept afterClusterTime and we have not identified any other that are problematic, so I am closing this ticket as Gone Away.

Comment by Kaloian Manassiev [ 27/Oct/17 ]

Some other commands, which should be considered:

  • replSetGetStatus
  • replSetHeartbeat
  • isMaster
Generated at Thu Feb 08 04:28:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.