[SERVER-28246] Remove configsvr metadata after v3.6 Created: 08/Mar/17  Updated: 27/Oct/23  Resolved: 09/Jun/17

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

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Sharding
Sprint: Sharding 2017-07-31
Participants:

 Description   

as it will be replaced with the new logicalTime metadata.

And replace the read afterOpTime to config server with time from LogicalClock.



 Comments   
Comment by Andy Schwerin [ 09/Jun/17 ]

I'm worried about the unnecessary waiting, myself. I'm going to close this ticket "WaD" for now.

Comment by Spencer Brody (Inactive) [ 08/Mar/17 ]

Something to keep in mind is that while using the logical clock instead of the config server optime should be correct, I believe it can introduce unnecessary waiting, as you might wind up waiting for an optime from a write that happened on a shard, not on the config server.

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