[SERVER-37173] rollbackViaRefetch should survive attempt to drop non-existent collection Created: 17/Sep/18  Updated: 29/Oct/23  Resolved: 11/Apr/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.11, 4.0.13

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Pavithra Vetriselvan
Resolution: Fixed Votes: 0
Labels: rbfz, replication-rollbackviarefetch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Repl 2019-03-11, Repl 2019-03-25, Repl 2019-04-08, Repl 2019-04-22
Participants:
Linked BF Score: 10

 Description   

If rollbackViaRefetch attempts to drop a collection and it does not exist (for example, because it was dropped by a previous rollback attempt), the rollback will fail. This is because we look up the namespace of the collection by UUID. If the collection does not exist, we use the empty string for the namespace. Then we attempt to acquire a database lock with an empty namespace, which fails.



 Comments   
Comment by Githook User [ 20/Aug/19 ]

Author:

{'username': 'pvselvan', 'email': 'pvselvan@umich.edu', 'name': 'Pavi Vetriselvan'}

Message: SERVER-37173 rollbackViaRefetch survives non-existent collection drop

(cherry picked from commit a13c018b51465b04027adee28fd79fd82ed4575b)
Branch: v4.0
https://github.com/mongodb/mongo/commit/901bc31cb9c4cdbd9ec162a1546a76d6fc546d4c

Comment by Githook User [ 11/Apr/19 ]

Author:

{'email': 'pvselvan@umich.edu', 'name': 'Pavi Vetriselvan', 'username': 'pvselvan'}

Message: SERVER-37173 rollbackViaRefetch survives non-existent collection drop
Branch: master
https://github.com/mongodb/mongo/commit/a13c018b51465b04027adee28fd79fd82ed4575b

Comment by Tess Avitabile (Inactive) [ 04/Apr/19 ]

Requesting backport to 4.0, since this has been an issue in BFs on the 4.0 branch.

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