[SERVER-33475] Retried findAndModify doesn't properly wait for writeConcern Created: 23/Feb/18  Updated: 29/Oct/23  Resolved: 29/Mar/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.6.3, 3.7.1
Fix Version/s: 3.6.5, 3.7.4

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-27067 Some Commands do not wait for write c... Closed
is related to SERVER-33232 _configCreateCollection should proper... Closed
is related to SERVER-33727 Do not wait for write concern if opTi... Closed
is related to SERVER-35387 Ensure retried commitTransaction comm... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: Sharding 2018-04-09
Participants:
Linked BF Score: 0

 Description   

Similar to SERVER-33232, a fully retried write (write was sent more than once to the server and no writes needs to be done at this moment because they were already completed in the previous attempts) will never acquire the global lock in mode X or IX, and will thus not satisfy this condition:

https://github.com/mongodb/mongo/blob/r3.7.1/src/mongo/db/service_entry_point_mongod.cpp#L356-L360



 Comments   
Comment by Githook User [ 16/Apr/18 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-33475 Make retried findAndModify correctly wait for writeConcern

(cherry picked from commit 6e8c03cbd1ea7262653997ceac3672f2a34c0821)
Branch: v3.6
https://github.com/mongodb/mongo/commit/e6ca5783790d696c0e13573728cf902081659043

Comment by Githook User [ 29/Mar/18 ]

Author:

{'email': 'randolph@10gen.com', 'name': 'Randolph Tan', 'username': 'renctan'}

Message: SERVER-33475 Make retried findAndModify correctly wait for writeConcern
Branch: master
https://github.com/mongodb/mongo/commit/6e8c03cbd1ea7262653997ceac3672f2a34c0821

Comment by Randolph Tan [ 09/Mar/18 ]

schwerin Yes, "fully retried write" is when the write was sent more than once to the server and no writes needs to be done at this moment because they were already completed in the previous attempts.

Comment by Andy Schwerin [ 08/Mar/18 ]

renctan, by "fully retried write", do you mean a retry of a write that completed successfully on its previous execution? Could you clarify the description, please?

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