fix(mongodb): lower indexBuildMinAvailableDiskSpaceMB to 5 GiB#2462
Conversation
Hello delthas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
The 10 GiB threshold set in #2436 (ZENKO-5295) matches or exceeds the free space of the demo/demolvm profiles' 10Gi MongoDB data volume (~9.5 GiB free after ext4 overhead) and 8Gi config volume (~7.5 GiB), so mongod refuses every index build on fresh installs. The ops-vault-create-indexes job then crash-loops and the MongoDbCreateIndexesFailed alert fires. Lower it to 5000 (~4.88 GiB): still comfortable headroom on every production SKU (smallest Mongo data volume is 119Gi) while fitting under the smaller demo/CI volumes. Issue: ZENKO-5315
231ea68 to
dc709f4
Compare
Issue: ZENKO-5315
|
/create_integration_branches |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
|
/approve |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
This pull request did not target the following hotfix branch(es) so they
Please check the status of the associated issue ZENKO-5315. Goodbye delthas. The following options are set: approve, create_integration_branches |
Summary
Lower
MONGODB_INDEX_BUILD_MIN_DISK_SPACE_MBfrom10000to5000insolution-base/build.sh.#2436 (ZENKO-5295) added
--setParameter indexBuildMinAvailableDiskSpaceMB=10000to config servers and shard data servers. MongoDB reads this value as MiB, so it requires10000 * 1048576= ~9.77 GiB of free space before it will start any index build.That's fine on every production SKU (the smallest Mongo data volume across all installer profiles is 119Gi), but the
demo/demolvmprofiles provision only a 10Gi data volume (8Gi config). After ext4 overhead a fresh volume has ~9.5 GiB / ~7.5 GiB free — below the 9.77 GiB threshold — so on fresh demo/CI/AWS installs mongod refuses everycreateIndexes, theartesca-data-ops-vault-create-indexesjob crash-loops, and theMongoDbCreateIndexesFailedalert fires.5000(~4.88 GiB) fits under both demo volumes while keeping meaningful headroom on all production SKUs.Related
Issue: ZENKO-5315