-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Labels:
-
Fully Compatible
-
Sharding 2017-10-23, Sharding 2017-11-13
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.