Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.4.14, 3.5.8
Affects Version/s: None
Component/s: Storage
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v3.4
Sprint:
Storage 2017-05-08, Storage 2017-05-29
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

Non-atomic applyOps commands should not suppress normal oplog generation and then record a single applyOps command in the oplog, but instead log the individual commands.

is duplicated by

SERVER-19768 Failed applyOps command does not create an oplog entry even with some successful writes

Closed

related to

SERVER-36944 applyOps does not permit unknown field names when creating a v:1 index

Closed

SERVER-37333 [3.4] applyOps does not validate background index spec for system.indexes inserts

Closed

SERVER-29802 Non-atomic applyOps command should not take out a global exclusive lock

Closed

Assignee:: Maria van Keulen
Reporter:: Geert Bosch
Participants:: Eric Milkie, Geert Bosch, Githook User, Maria van Keulen, Spencer Brody
Votes:: 0 Vote for this issue
Watchers:: 15 Start watching this issue

Created:: Apr 03 2017 07:55:07 PM UTC
Updated:: Dec 18 2018 12:22:23 AM UTC
Resolved:: May 17 2017 03:30:16 PM UTC
Confidence Status Last Update:: 28/Apr/17 5:53 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates