Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feat] Need functionality added to check /proc/cpuinfo for MongoDB required flags #66

Open
ghost opened this issue Feb 2, 2022 · 0 comments
Labels
◼ Type: Enhancement This issue relates to a feature/improvement of a feature.

Comments

@ghost
Copy link

ghost commented Feb 2, 2022

Expected Behavior
The delegate owner should be warned that their server will not run MongoDB 5.0.5 due to the limitations of their processor.

Current Behavior
Delegate owners are only informed of the processor requirements when MongoDB fails to start after an upgrade/install, requiring a back out procedure.

Possible Solution
There should be a notification written into either the install/upgrade script or into xcash-dpops itself to check the /proc/cpuinfo flags and determine if the cpu meets the requirements of MongoDB 5.0.5 (namely the AVX flag, and possibly the SSE). If in the script, you should consider whether you want to block installations up front so that no update occurs at all on an invalid server and requires them to fix it first. If in xcash-dpops it should display the warning periodically (per block?) indicating that the cpu is missing the flags required by MongoDB and therefor this processor/system should be considered deprecated and efforts to replace it should start immediately.

Context
Encountered a failed delegate situation after an older server I was running did not meet MongoDB 5.0.5 processor requirements and would not start MongoDB.

@ghost ghost added the ◼ Type: Enhancement This issue relates to a feature/improvement of a feature. label Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
◼ Type: Enhancement This issue relates to a feature/improvement of a feature.
Projects
None yet
Development

No branches or pull requests

0 participants