[SERVER-28445] Get operationTime for command error response using _computeOperationTime Created: 23/Mar/17  Updated: 06/Dec/17  Resolved: 06/Jun/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.5.9

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Misha Tyulenev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-06-19
Participants:

 Description   

Right now in the catch block of mongo::execCommandDatabase in src/mongo/db/commands/dbcommands.cpp the operationTime is set to the current clusterTime. This is correct, but can result in extra waiting on subsequent afterClusterTime reads. Once the exception handling path is moved into Command::run, the operationTime should be found using the _computeOperationTime function. This is because _computeOperationTime requires the startOperationTime and the readConcern level.



 Comments   
Comment by Githook User [ 06/Jun/17 ]

Author:

{u'username': u'mikety', u'name': u'Misha Tyulenev', u'email': u'misha@mongodb.com'}

Message: SERVER-28445 Compute operationTime in command error response
Branch: master
https://github.com/mongodb/mongo/commit/c8f627994e2fb61ede198d9b27d5d7335a3d0d2b

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