[SERVER-53564] rollbackViaRefetch should use UUID when creating a collection during upsert Created: 04/Jan/21  Updated: 06/Dec/22  Resolved: 07/Jan/21

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

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

Assigned Teams:
Replication
Operating System: ALL
Sprint: Repl 2021-01-25
Participants:

 Description   

RollbackViaRefetch only sets the collection namespace on a request and does not set a UUID.

When attempting to create a collection on the rollback node during an upsert, we later hit a uassert because we are not primary and we did not pass in a UUID.

Since the rollback node is creating a collection it sees on the new primary, it should be using the same UUID.

Currently, the rollback attempt will fail, but is not marked unrecoverable. Subsequent rollback attempts can invariant, one example being the second rollback attempt trying to find a collection that was already dropped in the unsuccessful attempt.


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