Skip to content

fix(mongodb): lower indexBuildMinAvailableDiskSpaceMB to 5 GiB#2462

Merged
bert-e merged 2 commits into
development/2.15from
bugfix/ZENKO-5315/mongo-index-build-disk-threshold
Jul 10, 2026
Merged

fix(mongodb): lower indexBuildMinAvailableDiskSpaceMB to 5 GiB#2462
bert-e merged 2 commits into
development/2.15from
bugfix/ZENKO-5315/mongo-index-build-disk-threshold

Conversation

@delthas

@delthas delthas commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Summary

Lower MONGODB_INDEX_BUILD_MIN_DISK_SPACE_MB from 10000 to 5000 in solution-base/build.sh.

#2436 (ZENKO-5295) added --setParameter indexBuildMinAvailableDiskSpaceMB=10000 to config servers and shard data servers. MongoDB reads this value as MiB, so it requires 10000 * 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 / demolvm profiles 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 every createIndexes, the artesca-data-ops-vault-create-indexes job crash-loops, and the MongoDbCreateIndexesFailed alert fires.

5000 (~4.88 GiB) fits under both demo volumes while keeping meaningful headroom on all production SKUs.

Related

Issue: ZENKO-5315

@bert-e

bert-e commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Hello delthas,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@delthas delthas requested review from a team, DarkIsDude and benzekrimaha July 9, 2026 10:05
@scality scality deleted a comment from bert-e Jul 9, 2026
@bert-e

bert-e commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

Comment thread solution-base/build.sh Outdated
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
@delthas delthas force-pushed the bugfix/ZENKO-5315/mongo-index-build-disk-threshold branch from 231ea68 to dc709f4 Compare July 10, 2026 08:14
@delthas

delthas commented Jul 10, 2026

Copy link
Copy Markdown
Contributor Author

/create_integration_branches

@bert-e

bert-e commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/2.10
  • development/2.11
  • development/2.12
  • development/2.13
  • development/2.14
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: create_integration_branches

@bert-e

bert-e commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

The following options are set: create_integration_branches

@delthas

delthas commented Jul 10, 2026

Copy link
Copy Markdown
Contributor Author

/approve

@bert-e

bert-e commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/2.15

  • ✔️ development/2.16

The following branches have NOT changed:

  • development/2.10
  • development/2.11
  • development/2.12
  • development/2.13
  • development/2.14
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

This pull request did not target the following hotfix branch(es) so they
were left untouched:

  • hotfix/2.13.5

Please check the status of the associated issue ZENKO-5315.

Goodbye delthas.

The following options are set: approve, create_integration_branches

@bert-e bert-e merged commit 5508674 into development/2.15 Jul 10, 2026
22 checks passed
@bert-e bert-e deleted the bugfix/ZENKO-5315/mongo-index-build-disk-threshold branch July 10, 2026 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants