[SERVER-31492] Fix so replication coordinator doesn't attempt to connect to self on bind_ip 0.0.0.0 and initialize legacy transport layer synchronously so connections are not done too early. Created: 10/Oct/17  Updated: 30/Oct/23  Resolved: 12/Oct/17

Status: Closed
Project: Core Server
Component/s: Networking, Replication
Affects Version/s: None
Fix Version/s: 3.6.0-rc1

Type: Bug Priority: Major - P3
Reporter: Henrik Edin Assignee: Henrik Edin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platforms 2017-10-23
Participants:
Linked BF Score: 0

 Comments   
Comment by Githook User [ 12/Oct/17 ]

Author:

{'email': 'henrik.edin@mongodb.com', 'name': 'Henrik Edin', 'username': 'henrikedin'}

Message: SERVER-31492 Make TransportLayerLegacy::start block until we are ready to accept connections.
Fix bug in the replication coordinator where it attempted to make connections to self if we are bound to 0.0.0.0.
Branch: master
https://github.com/mongodb/mongo/commit/c7286b34045fcf8c4b3d8b7d1c275a708f671ee5

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