[SERVER-84812] Associate SocketException with a HostAndPort Created: 15/Jun/23  Updated: 12/Jan/24  Resolved: 15/Jun/23

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

Type: Bug Priority: Major - P3
Reporter: Alex Li Assignee: Alex Li
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-78148 Associate SocketException with offend... Closed
Participants:

 Description   

Currently, the NetworkInterfaceTL returns SocketException as a status, which is converted to a RemoteCommandResponse without HostAndPort. It is useful to know exactly which HostAndPort caused this issue.

Making this change caused some issues with ReplicaSetMonitor (probably expecting a Status instead of RemoteCommandResponse on hello or pings). Fix this and other issues that appear due to this change. 

In AsyncRPC and AsyncRequestsSender, because no HostAndPort associates with SocketException/HostUnreachable, the HostAndPort used to update the ReplicaSetMonitor is (wrongly) the first HostAndPort in RemoteCommandRequest's target vector. This target is arbitrary and could be wrong.


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