[SERVER-47394] Have servers close connections on a SplitHorizonChange error for awaitable isMaster Created: 07/Apr/20  Updated: 29/Oct/23  Resolved: 22/Apr/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.5 Required, 4.4.0
Fix Version/s: 4.4.0-rc4, 4.7.0

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

Issue Links:
Backports
Depends
Related
is related to SERVER-46893 Allow streamable isMaster to wait on ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Repl 2020-04-20, Repl 2020-05-04
Participants:

 Comments   
Comment by Githook User [ 04/May/20 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@10gen.com', 'username': 'jasonjhchan'}

Message: SERVER-47394 Disconnect from client on SplitHorizonChange error

(cherry picked from commit 39f506463b2a88310ec874330347f1fd3ce07778)
Branch: v4.4
https://github.com/mongodb/mongo/commit/47b3bc5d5927225bb1fd7767613b1cf74157f7c9

Comment by Githook User [ 22/Apr/20 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@10gen.com', 'username': 'jasonjhchan'}

Message: SERVER-47394 Disconnect from client on SplitHorizonChange error
Branch: master
https://github.com/mongodb/mongo/commit/39f506463b2a88310ec874330347f1fd3ce07778

Comment by Jason Chan [ 07/Apr/20 ]

A relevant piece of code to look at would be here where we close the socket when certain exceptions are thrown to the top of the loop.

An alternative is to add a flag to the opCtx to indicate we should close the socket connection.

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