[SERVER-28012] Make ShardLocal stateless: remove ShardLocal::_lastOpTime field Created: 14/Feb/17  Updated: 05/Apr/17  Resolved: 15/Feb/17

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done before SERVER-27860 Enable ShardLocal on shards Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

This is so that we can create an instance of ShardLocal on the stack whenever we need to use it, rather than do all reads/writes through a single instance of ShardLocal.

The last optime is the only state that ShardLocal maintains, and rather than have ShardLocal and ReplicationCoordinator both maintain the latest optime, the ReplicationCoordinator should just be used by ShardLocal to get the latest optime.


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