[SERVER-39480] Log network failure status in DBClientConnection Created: 08/Feb/19  Updated: 29/Oct/23  Resolved: 04/Jun/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.0.11, 4.2.0-rc1, 4.3.1

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Rahul Sundararaman (Inactive)
Resolution: Fixed Votes: 1
Labels: neweng, sa-intern-tickets
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-35370 network error while attempting to run... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2, v4.0
Sprint: Service Arch 2019-06-03, Service Arch 2019-06-17
Participants:

 Description   

In DBClientConnect::call(), when we get statuses from sinkMessage() and sourceMessage() we reduce them to a boolean value and throw away the reason. We can at least log the message before we walk away.



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

Author:

{'name': 'Rahul Sundararaman', 'email': 'rahul.sundararaman@Rahuls-MacBook-Pro.local'}

Message: SERVER-39480 Added log messages for failing DBClientConnection

(cherry picked from commit 928aabbaf9444005fa4fafb399244ce6d475eb9f)
Branch: v4.0
https://github.com/mongodb/mongo/commit/b7dc81fab14c6e52ee5116c2d1edc96b41127a71

Comment by Githook User [ 03/Jun/19 ]

Author:

{'name': 'Rahul Sundararaman', 'email': 'rahul.sundararaman@Rahuls-MacBook-Pro.local'}

Message: SERVER-39480 Added log messages for failing DBClientConnection
Branch: master
https://github.com/mongodb/mongo/commit/928aabbaf9444005fa4fafb399244ce6d475eb9f

Comment by Benjamin Caimano (Inactive) [ 11/Feb/19 ]

kelsey.schubert, this is the ticket I mentioned on Friday. For reference, this leads to messages that look like this:

Error: error doing query: failed: network error while attempting to run command 'createIndexes' on host ...

I believe that the actual error that caused that one was ErrorCodes::InterruptedDueToStepDown. Which yes, it did happen over the network, but we've lost some details.

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