[SERVER-33177] Inconsistent handling of operation time in mongod error response Created: 07/Feb/18  Updated: 09/Jul/18  Resolved: 09/Jul/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.6.3, 3.7.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Cheahuychou Mao
Resolution: Duplicate Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-34843 Mongod can return operationTime great... Closed
Operating System: ALL
Participants:

 Description   

There is a logic in execCommandDatabase to differentiate between whether there is a valid operationTime:
https://github.com/mongodb/mongo/blob/62ca1bcdd3dcc634a6fa91204b0f0941eb76399e/src/mongo/db/service_entry_point_mongod.cpp#L723

However, the logic does not exist in runCommands:
https://github.com/mongodb/mongo/blob/62ca1bcdd3dcc634a6fa91204b0f0941eb76399e/src/mongo/db/service_entry_point_mongod.cpp#L815

This is inconsistent as runCommands calls execCommandDatabase and should therefore have the same logic.



 Comments   
Comment by Jack Mulrow [ 09/Jul/18 ]

The issue described in this ticket was resolved by the fix for SERVER-34843.

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