Detect MongoDB AVX failures and provide clear guidance #50
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tForTCPOrExit for process readiness
Merging this branch changes the coverage (1 decrease, 1 increase)
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to PR #39
Summary
Detect MongoDB AVX failures immediately during startup and provide clear, actionable guidance instead of a confusing 3-minute TCP timeout.
Problem
MongoDB 5.0+ requires AVX CPU instructions. On CPUs without AVX (older hardware, VMs, budget processors), MongoDB crashes with SIGILL before writing any logs. Users wait 180 seconds and see a useless timeout error.
Solution
Monitor infrastructure processes during TCP readiness wait. If a process dies, detect it immediately and check for SIGILL (illegal instruction). Display a clear error message with solutions.