-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.2.0
-
Component/s: Diagnostics, Sharding
-
None
-
Fully Compatible
-
ALL
-
v4.2
-
Service Arch 2020-01-13, Service Arch 2020-01-27
The schema for metrics under connPoolStats.connectionsInUsePerPool.NetworkInterfaceTL-TaskExecutorPool-0 changes frequently as it appears that hosts in that tree are emitted in an order that changes every couple of samples, and hosts come and go frequently from the metrics. These frequent schema changes greatly reduce compression efficiency, limiting the retention period - as short as 15 hours in one case. The schema for this subtree should be monotonic and consistent from one sample to the next.
- is related to
-
SERVER-36099 FTDC for mongos is unworkably large for large installations
- Closed
-
SERVER-42125 Avoid increasing connection count to passive secondaries with matchPrimaryNode
- Closed
-
SERVER-45546 Do not create HostPools for passive members
- Closed