[SERVER-39089] Collection drops are not replicated under protocol version 0 Created: 18/Jan/19  Updated: 06/Dec/22  Resolved: 07/Feb/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.6.0, 3.6.9
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-39651 drop pending collection dose not clea... Closed
Related
Assigned Teams:
Replication
Operating System: ALL
Participants:
Case:

 Description   

Create a replica set on 3.6.9 and configure it to run protocol version 0, then create a collection and drop it. The mongod log on the secondaries show the following messages

2019-01-18T13:11:36.368-0500 I COMMAND  [repl writer worker 0] CMD: drop test.c91
2019-01-18T13:11:36.368-0500 I STORAGE  [repl writer worker 0] dropCollection: test.c91 (230159df-a788-4c1c-a5bd-22161ea8a674) - renaming to drop-pending collection: test.system.drop.1547835095i373t-1.c91 with drop optime { ts: Timestamp(1547835095, 373), t: -1 }

but there is no "completing collection drop" message, and the WT table is never dropped on the secondary.



 Comments   
Comment by Gregory McKeon (Inactive) [ 07/Feb/19 ]

We won't be doing additional work on PV0. The workaround is to upgrade to PV1.

Comment by Bruce Lucas (Inactive) [ 18/Jan/19 ]

Yes indeed it does.

Comment by Judah Schvimer [ 18/Jan/19 ]

I think secondaries do not advance the commit point in PV0, which would explain why this happens. bruce.lucas, when the secondary is elected primary, does it suddenly drop all of the collections it didn't drop as a secondary?

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