[SERVER-33015] API to get/set lastCommittedOpTime in ReplicaSetMonitor. Created: 30/Jan/18  Updated: 27/Oct/23  Resolved: 01/Feb/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

Assigned Teams:
Sharding
Sprint: Sharding 2018-02-12
Participants:

 Comments   
Comment by Jack Mulrow [ 01/Feb/18 ]

The initial implementation of lastCommittedOpTime tracking on mongos will just store the highest seen value per shard in the Shard class, so there is no need to update the replica set monitor. We may come back to this if we decide it would be useful to store the lastCommittedOpTime per node instead.

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