[SERVER-69813] Get rid of temporary solution for stuck secondaries Created: 19/Sep/22  Updated: 26/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Antonio Fuschetto Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-42737 MongoDB stuck on update metadata Closed
Assigned Teams:
Catalog and Routing
Participants:

 Description   

Starting from 4.0 version, a temporary solution has been implemented to resolve the problem described in SERVER-42737, i.e., the catalog refresh on secondaries stuck waiting for a notification which not arrive (see this analysis for further details).

The original idea was to get rid of this solution after implementing the catalog loader writes with transactions (see SERVER-44105, closed as "Won't Do"). Nonetheless, the current plan is to remove the ShardServerCatalogLoader (see PM-2948), which should allow to get rid of the temporary solution mentioned above.


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