[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: |
|
||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| 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
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? |