[SERVER-28646] Don't report ops as passed if logOps causes txn to fail Created: 06/Apr/17  Updated: 15/Aug/17  Resolved: 09/Apr/17

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.4.4, 3.5.6

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

Issue Links:
Backports
Related
is related to SERVER-28645 Fail commands that require too many l... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4
Sprint: Storage 2017-04-17
Participants:

 Description   

If individual operations of an atomic applyOps command succeed, but are rolled back as result of a later error, make sure to not return a results field that marks those commands as successful.

Currently we insert a new results field, but that does not replace the original one. Instead only add the results field on successfully committing the transaction.



 Comments   
Comment by Githook User [ 11/Apr/17 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-28646 Don't report ops as passed if logOps causes txn to fail

(cherry picked from commit d17d4907001cb02e3697148df4b3016ac232d0a1)

Conflicts:
src/mongo/db/catalog/apply_ops.cpp
Branch: v3.4
https://github.com/mongodb/mongo/commit/2206856999b0f9eb5a6b83f2da740efceeca1387

Comment by Githook User [ 09/Apr/17 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-28646 Don't report ops as passed if logOps causes txn to fail
Branch: master
https://github.com/mongodb/mongo/commit/d17d4907001cb02e3697148df4b3016ac232d0a1

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