[SERVER-48985] Add logging for failCommand Created: 18/Jun/20  Updated: 29/Oct/23  Resolved: 26/Jun/20

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

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Benjamin Caimano (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-48932 ReplicaSetMonitor hitting failpoint s... Closed
Problem/Incident
causes SERVER-49220 failCommand with appName does not fai... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Service arch 2020-06-29
Participants:

 Description   

There are a lot of different conditions where the failCommand failpoint can activate. We should add logging to make it obvious why it happened.



 Comments   
Comment by Benjamin Caimano (Inactive) [ 29/Jun/20 ]

divjot.arora shane.harvey, this should be available on r4.4.0-rc12.

Comment by Githook User [ 29/Jun/20 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-48985 Add logging for failCommand
Branch: v4.4
https://github.com/mongodb/mongo/commit/da34c52b41b69ce9c0a92531c51e66c4f847aab8

Comment by Githook User [ 25/Jun/20 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-48985 Add logging for failCommand
Branch: master
https://github.com/mongodb/mongo/commit/56f5500860e0933863ba32d8969a58c848b1b8fa

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