[SERVER-47351] Better synchronize NetworkInterfaceTL shutdown with in-flight commands Created: 06/Apr/20  Updated: 29/Oct/23  Resolved: 07/Apr/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.2.7, 4.4.0-rc3, 4.7.0

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Benjamin Caimano (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-47507 Cancel all remaining egress commands ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4, v4.2
Sprint: Service arch 2020-04-20
Participants:
Linked BF Score: 76

 Description   

We check immediately for shutdown during startCommand() here. Unfortunately, that doesn't synchronize with how we track commands here.



 Comments   
Comment by Githook User [ 28/Apr/20 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-45117 SERVER-47351 SERVER-47507 Guard NetworkInterfaceTL shutdown for alarms and commands

These three tickets were originally committed separately to v4.4 and
master. However, they build upon each other to throughly shutdown our
NetworkInterfaces upon shutdown.
Branch: v4.2
https://github.com/mongodb/mongo/commit/00b2ba7b26021582bf5d26adb2223568d3362fe9

Comment by Githook User [ 23/Apr/20 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-47351 Better synchronize NetworkInterfaceTL shutdown with in-flight commands
Branch: v4.4
https://github.com/mongodb/mongo/commit/2335687a9331a16b15fe25ac07a2433853b52f97

Comment by Githook User [ 06/Apr/20 ]

Author:

{'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}

Message: SERVER-47351 Better synchronize NetworkInterfaceTL shutdown with in-flight commands
Branch: master
https://github.com/mongodb/mongo/commit/d7af6ab17c584a5602e1fb10d89bb9242bb35985

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