[SERVER-28594] non-atomic applyOps should log each individual op Created: 03/Apr/17  Updated: 18/Dec/18  Resolved: 17/May/17

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.4.14, 3.5.8

Type: Bug Priority: Major - P3
Reporter: Geert Bosch Assignee: Maria van Keulen
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-19768 Failed applyOps command does not crea... Closed
Related
related to SERVER-36944 applyOps does not permit unknown fiel... Closed
related to SERVER-37333 [3.4] applyOps does not validate back... Closed
related to SERVER-29802 Non-atomic applyOps command should no... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4
Sprint: Storage 2017-05-08, Storage 2017-05-29
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 12/Feb/18 ]

Author:

{'email': 'louis.williams@mongodb.com', 'name': 'Louis Williams', 'username': 'louiswilliams'}

Message: SERVER-28594 non-atomic applyOps should log each operation individually

(cherry picked from commit 975804ed16ed446e32e7e73643188c9276686311)
Branch: v3.4
https://github.com/mongodb/mongo/commit/4b2f7438ec3494cdf5f4f996bc1ac955a0698f40

Comment by Githook User [ 17/May/17 ]

Author:

{u'username': u'mvankeulen94', u'name': u'Maria van Keulen', u'email': u'maria@mongodb.com'}

Message: SERVER-28594 Log each individual non-atomic op in applyOps
Branch: master
https://github.com/mongodb/mongo/commit/975804ed16ed446e32e7e73643188c9276686311

Comment by Eric Milkie [ 05/Apr/17 ]

I think SERVER-19768 will be fixed automatically if we implement the suggestion in this ticket.

Comment by Spencer Brody (Inactive) [ 05/Apr/17 ]

Would be awesome if whoever fixes could fix SERVER-19768 while they were at it if it winds up easy to do so.

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