[SERVER-31328] Don't fetch oplog entries for retries of executed inserts or deletes Created: 29/Sep/17  Updated: 30/Oct/23  Resolved: 23/Oct/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.6.0-rc1

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-10-23, Sharding 2017-11-13
Participants:

 Description   

Right now retrying a successful write requires fetching the oplog entry for each completed statement. Since the oplog entry isn't necessary to build the response for inserts and deletes (both just set the n field to 1, here and here), Session::checkStatementExecuted can skip fetching the oplog entry for those commands, which should make no-op retries faster.



 Comments   
Comment by Githook User [ 23/Oct/17 ]

Author:

{'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}

Message: SERVER-31328 Don't fetch oplog entries for retries of executed inserts or deletes
Branch: master
https://github.com/mongodb/mongo/commit/aa95387d1a8fb475c267a3ca0e84a1b4a18a7ace

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