[SERVER-58247] Using createIndexes in applyOps with the oplog application mode set on primary should uassert, not fassert Created: 02/Jul/21  Updated: 06/Dec/22  Resolved: 06/Jul/21

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

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto 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
Related
is related to SERVER-32952 applyOps does not validate updates Backlog
is related to SERVER-53674 Do not run applyOps commands in the f... Closed
is related to SERVER-36263 Bypassing operation validation in app... Closed
Assigned Teams:
Replication
Operating System: ALL
Participants:
Linked BF Score: 42

 Description   

It's not legal to use the applyOps command to execute createIndexes, and we have a uassert to prevent that. But if we explicitly set the application mode in the applyOps command to InitialSync (probably also recovery or steady-state), we bypass that check and, on the primary, instead hit an fassert. We should uassert in this situation instead.



 Comments   
Comment by Judah Schvimer [ 06/Jul/21 ]

We will do SERVER-53674 instead to stop the BFs. The user risk was already mitigated in SERVER-36263 by putting applyOps behind a special privilege.

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