Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Won't Fix
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Replication
Operating System:
ALL
Linked BF Score:
42
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

is related to

SERVER-32952 applyOps does not validate updates

Backlog

SERVER-53674 Do not run applyOps commands in the fuzzer

Closed

SERVER-36263 Bypassing operation validation in applyOps should require special privilege

Closed

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: Matthew Russotto
Participants:: [DO NOT USE] Backlog - Replication Team, Judah Schvimer, Matthew Russotto
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Jul 02 2021 04:09:43 PM UTC
Updated:: Dec 06 2022 01:09:07 AM UTC
Resolved:: Jul 06 2021 06:22:25 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates