[SERVER-63951] dbCheck should handle concurrent replacement of collection with view on same namespace Created: 23/Feb/22  Updated: 11/Aug/23  Resolved: 10/Aug/23

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

Type: Bug Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Moustafa Maher
Resolution: Duplicate Votes: 0
Labels: pm-855-quick-win
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-79490 Dbcheck should not fail with CommandN... Closed
Related
related to SERVER-79923 Complete TODO listed in SERVER-63951 Closed
Assigned Teams:
Replication
Operating System: ALL
Participants:

 Description   

Currently, if a collection is dropped and then a view is created on the same namespace, this can cause problems for dbCheck. It looks like if this happens in between when dbCheck takes its inventory and when it actually attempts to run on the replaced collection, we will currently report this as a data inconsistency, as we will get a CommandNotSupportedOnView error.



 Comments   
Comment by Dan Larkin-York [ 23/Feb/22 ]

SERVER-57250 adds an FSM workload that concurrently creates views and collections on the same namespace to stress-test the catalog. This test has to be excluded from any suite which runs dbCheck in the background. After this behavior is properly supported by dbCheck, we should re-enable the test in all the relevant suites.

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