Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Fully Compatible
-
ALL
-
v4.2
-
Service Arch 2019-12-30, Service Arch 2020-01-13, Service Arch 2020-01-27
Description
Calls to NetworkInterfaceTL::startCommand() before NetworkInterfaceTL::startup() wil cause crashes (due to an assumption inside NetworkInterfaceTL::startCommand() that we have a connection pool.
That's out of contract for a NetworkInterface
/** |
* Starts up the network interface.
|
*
|
* It is valid to call all methods except shutdown() before this method completes. That is,
|
* implementations may not assume that startup() completes before startCommand() first
|
* executes.
|
*
|
* Called by the owning TaskExecutor inside its run() method.
|
*/
|
virtual void startup() = 0; |
To fix that, lets create more state on the NiTL in it's ctor, and only spin up the background thread in startup().
Attachments
Issue Links
- is duplicated by
-
SERVER-47541 mongod segfaults during mongot e2e tests
-
- Closed
-
- related to
-
SERVER-47541 mongod segfaults during mongot e2e tests
-
- Closed
-