-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.3.3
-
Component/s: Testing Infrastructure
-
None
-
Fully Compatible
-
ALL
-
v4.4
-
-
Sharding 2020-02-24, Sharding 2020-03-09, Sharding 2020-03-23
-
19
The autosplit functionality is best effort. In fact if we run two insert that should both trigger trigger an autosplit on the same shard, it is not guarantee that the second insert will actually cause a chunk split.
This is the case when the second insert call a ChunkSplitStateDriver::tryInitiateSplit while a previous chunk split operation is still running. The second attempt will be simply abandoned without any retry logic.
This is similar to SERVER-43960, we need to call waitForOngoingChunkSplits() after every insertion.