|
I believe this request boils down to a change to the foreground index build's bucket fill percentage (by lowering it, or by adding jitter). Is that correct?
Background index builds are equivalent to inserting data records one by one into an empty index, so I believe that if you ran the reindex command for an index that was originally built in the background, you wouldn't see the same growth behavior.
I believe that in earlier versions of MongoDB, the bucket file percentage for foreground index builds was set the same as the bucket split percentage, but that ended up wasting a lot of space in indexes that never added new keys within the current keyspace. The current setting does not waste as much space for such workloads, at the expense of the growth behavior for evenly distributed keys as you have noted in the Description.
|