[SERVER-47061] Log all_durable timestamp on writeConcern failures if testCommand is enabled Created: 23/Mar/20  Updated: 29/Oct/23  Resolved: 23/Mar/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Repl 2020-04-06
Participants:
Linked BF Score: 0

 Description   

Log all_durable timestamp on writeConcern failures if testCommand is enabled to help debugging.



 Comments   
Comment by Githook User [ 24/Mar/20 ]

Author:

{'name': 'Lingzhi Deng', 'username': 'ldennis', 'email': 'lingzhi.deng@mongodb.com'}

Message: SERVER-47061: Log all_durable timestamp on writeConcern failures if testCommand is enabled

(cherry picked from commit 99065500588a7c7dfa4cf5c51df2e1ee99bf400f)
Branch: v4.4
https://github.com/mongodb/mongo/commit/13fa68bcc2cbe782076b46911723748547ca5dcd

Comment by Githook User [ 23/Mar/20 ]

Author:

{'email': 'lingzhi.deng@mongodb.com', 'name': 'Lingzhi Deng', 'username': 'ldennis'}

Message: SERVER-47061: Log all_durable timestamp on writeConcern failures if testCommand is enabled
Branch: master
https://github.com/mongodb/mongo/commit/99065500588a7c7dfa4cf5c51df2e1ee99bf400f

Generated at Thu Feb 08 05:13:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.