SERVER-130149In Code Review
Allow a running index build to pick up an increased maxIndexBuildMemoryUsageMegabytes value after a spill boundary
h2. Problem Today, when an index build enters a bad spill/merge-spill pattern, the operator may only discover that the configured memory limit is too low after the build has already started. In related cases, this has been called out as a practical problem because the need to raise {{maxIndexBuildMemoryUsageMegabytes}} often only becomes obvious once index builds are already in progress, at which point recovery can require restarting the broader operation. We also have evidence of index-buil