-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.2.0, 4.4.0, 5.0.0, 6.0.0, 7.0.0, 7.2.0-rc0
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
v7.3, v7.0, v6.0, v5.0
-
CAR Team 2024-01-08, CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19, CAR Team 2024-03-04
The balancer sporadically checks if all the shards in the cluster have the exact same binary version. When this is not the case, the balancer emits a warning log message.
This has two problems:
- Correctness:
During upgrade/downgrade procedure is totally expected that the shards in the cluster will have a mismatching binary version, thus I believe is incorrect to emit a warning log message. - Performance:
Even though the check is actually performed sporadically, the balancer collects the shards binary versions every round during construction of ClusterStatistics (this is actually done multiple times per round). The retrieval of binary version is done by executing the serverStatus command on all shard primaries, this is done serially. Thus, in a cluster with large number of shards, this can slow down significantly the balancer round.
- has to be done before
-
SERVER-87063 Split currSizeBytes out of ShardStatistics
- Closed
- is caused by
-
SERVER-8279 Warn or do not allow the balancer to balance when running in a mixed sharded cluster
- Closed