[SERVER-11211] Mongo improperly updates config.databases collection Created: 16/Oct/13  Updated: 06/Dec/22  Resolved: 15/Nov/18

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

Type: Bug Priority: Major - P3
Reporter: Charlie Page Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

The mongos due to errors, including network errors beyond our control, can have a wrong world view where databases that do exist are reported not to. When the database is accessed the mongos treats it like a new database. This leads to the mongos then upserting into the config.databases collection the wrong information: that the database named is non-sharded. This causes significant errors with mongodb systems.
If the mongos uses an insert against the config database which fails when a database with that name already exists, the mongos will properly get an error when it’s world view is incorrect, and will not corrupt the config server’s database. At this point the mongos should also reload it’s data so that it has a correct world view.

This change would isolate the error to the mongos instead of propagating it's error state to the entire system.



 Comments   
Comment by Gregory McKeon (Inactive) [ 15/Nov/18 ]

This will become impossible once we do PM-1051, so closing this ticket.

Generated at Thu Feb 08 03:25:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.