[SERVER-47323] If config.system.indexBuilds is dropped, then voteCommitIndexBuild will endlessly retry on NamespaceNotFound errors Created: 03/Apr/20  Updated: 15/Feb/22  Resolved: 15/Feb/22

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

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Vishnu Kaushik
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-48525 Forbid dropping config.transactions w... Closed
related to SERVER-49386 Always forbid dropping config.transac... Closed
related to SERVER-47635 Remove index build entries for the fi... Closed
related to SERVER-49052 Prohibit dropping the config db Closed
related to SERVER-53001 Complete TODO listed in SERVER-47323 Closed
related to SERVER-54789 add config db check to indexbuildentr... Closed
Operating System: ALL
Sprint: Execution Team 2020-06-29, Execution Team 2020-07-13, Execution Team 2020-07-27, Execution Team 2020-08-10, Execution Team 2020-09-21, Execution Team 2020-10-05
Participants:
Linked BF Score: 120

 Description   

The fuzzer dropped the config.system.indexBuilds collection and then an index build hangs retrying the voteCommitIndexBuild cmd.



 Comments   
Comment by Vishnu Kaushik [ 28/Sep/20 ]

TIG-2675 blocklisted the config.system.indexBuilds from being dropped in the fuzzer. The access control mechanism already forbids dropping any "system." collection. 

Comment by Suganthi Mani [ 01/Jul/20 ]

FYI, We also have a repl ticket SERVER-48525 where dropping of config.transactions lead to unexpected consequences.

EDIT: SERVER-49386 - Always forbid dropping config.transactions

Comment by Gregory Wlodarek [ 23/Jun/20 ]

michael.gargiulo is going to investigate from a product standpoint whether we can prohibit the config database from being dropped as a way to resolve this issue.

Comment by Suganthi Mani [ 06/May/20 ]

To drop the config.system.indexBuilds database, we would need to drop the config database outside a session. This can be done in a shell started with the --disableImplicitSessions option.

I am wondering if we are also able to remove admin database with  --disableImplicitSessions option. To me, both admin and config databases are internal and should not be tampered by user.

Generated at Thu Feb 08 05:13:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.