[SERVER-60603] Allow connection reset errors without assertion in ASIOSession::ensureSync() Created: 11/Oct/21  Updated: 29/Oct/23  Resolved: 29/Nov/21

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

Type: Bug Priority: Major - P3
Reporter: Blake Oler Assignee: Tyler Seip (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-57466 Swallow connection reset-related erro... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0
Sprint: Service Arch 2021-11-15, Service Arch 2021-11-22, Service Arch 2021-12-13
Participants:
Linked BF Score: 137
Story Points: 3

 Description   

In a similar fashion to SERVER-57466, an error caused by a connection reset while attempting to setSocketOption inside AsioSession::ensureSync() can cause a tassert.

The solution to this ticket should be the same as what ends up being committed in SERVER-57466.



 Comments   
Comment by Githook User [ 29/Nov/21 ]

Author:

{'name': 'Tyler Seip', 'email': 'Tyler.Seip@mongodb.com', 'username': 'tseip-mongo'}

Message: SERVER-60603: Allow connection reset errors without assertion in ASIOSession::ensureSync()
Branch: master
https://github.com/mongodb/mongo/commit/d2bca5f1c72212d05dd99a22b5ee1b283ecb65ed

Comment by Blake Oler [ 19/Nov/21 ]

My WIP branch – the solution is correct, and the test is roughly what I'd want to test, but it needs to be brought up to date with Billy's changes to the tests.

CC tyler.seip

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