|
As misha.tyulenev said, the problem is that ShardingTest is starting first the router then the config servers and then the shards. This means that when the mongos starts it doesn't know that the autosplit needs to be enabled and it will fetch that configuration parameter from the config server later on through the sharding uptime reporter thread.
In 4.0 the autosplitter was operating on the mongos, on 4.2 on both mongos and the shards and as of 4.4, the autosplitter is operating only on the shards. This explain why this test failed just once in the 4.2 branch and only on the sharding_last_stable_mongos_and_mixed_shards suite. In fact in this specific scenario the router is running with v4.0 and is in charge for the autosplitting.
Given that this issue:
- Doesn't affect any version grater then 4.0.
- Is not a problem on production system.
- There is not an easy fix for this and all the solution I discussed with matthew.saltz required a lot of changes or dirty hacks.
We decided not to fix this.
|