-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2025-10-27, CAR Team 2025-11-10, CAR Team 2025-11-24, CAR Team 2025-12-08, CAR Team 2025-12-22
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In this ticket, we should update the transport layer to be able to accept new connections and start new sessions from the maintenance port. Connections via the new port should be prioritized or should be handled separately from connections on the main port in order to prevent connections on the maintenance port from being impacted by those on the main port.
- depends on
-
SERVER-112360 Extend Transport Layer Manager to support maintenance port
-
- Closed
-
- is depended on by
-
SERVER-114059 Update quorum checking to use the maintenance port
-
- Closed
-
-
SERVER-112859 Exempt connections from maintenance port from rate limiters
-
- In Code Review
-
-
SERVER-113219 Exempt connections on the maintenance port from the connection limit
-
- In Code Review
-
-
SERVER-113221 Migrate replication internals to use maintenance port
-
- In Code Review
-
-
SERVER-112860 Add new server status metric to track maintenance port connections
-
- Closed
-
-
SERVER-113220 Improve observability for connections via the maintenance port
-
- Closed
-
- is duplicated by
-
SERVER-107363 Dedicated connection port for internal maintenance operations
-
- Closed
-
- is related to
-
SERVER-115111 Investigate why occasionally the unix domain socket under /tmp is missing
-
- Open
-