[SERVER-72709] Should dropDatabase remove the views collection first to maintain the same oplog entry order for time-series namespace as dropCollection? Created: 10/Jan/23  Updated: 19/Jan/23  Resolved: 19/Jan/23

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

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

Issue Links:
Duplicate
duplicates SERVER-71937 Validating a time-series view cannot ... Closed
Assigned Teams:
Storage Execution
Sprint: Execution Team 2023-01-23
Participants:

 Description   

The dropCollection and dropDatabase cmds write oplog entries for time-series collections in different orders.

dropCollection writes
1) a view entry delete oplog entry and then
2) a buckets drop oplog entry

dropDatabase writes
1) a buckets drop oplog entry and then
2) removes the view entry by dropping the database-wide views collection

Discussion on slack led to the thought that we tried to ensure an order, such that the buckets collection may remain without the view, but not the other way around. But there's uncertainty as to whether or not it matters.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 19/Jan/23 ]

This was spun off during the investigation of SERVER-71937. But the solution to SERVER-71937 is going to do what this ticket proposes.

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