Closed kenny19850514 closed 2 years ago
Hi,
Could you try it again without using the NFS storage class? Just to confirm that the issue is there
mongodb 5 on x86 requires a cpu with avx, check your cpu flags of the kubernetes node with lscpu | grep avx
mongodb 5 on x86 requires a cpu with avx, check your cpu flags of the kubernetes node with
lscpu | grep avx
This was my problem. I went back to the 4.4 version
As Luca explained, mongodb 5.0 requires a CPU with AVX support on x86 architectures
mongodb 5 on x86 requires a cpu with avx, check your cpu flags of the kubernetes node with
lscpu | grep avx
Brilliant! Failed to deploy mongodb on an Intel J6412/K3D setup, let me fallback to csv data source for running my backtesting apps. LOL
As Luca explained, mongodb 5.0 requires a CPU with AVX support on x86 architectures
Hi @fmulero
How did you manager to change the version ? helm install mongodb TrueCharts/mongodb
Do you use values.yaml file ? I can't see the parameter for version in there https://github.com/truecharts/charts/blob/master/charts/dependency/mongodb/values.yaml
Please see helm documentation
@fmulero, There is an option to take my patch to automate the build without Sandy Bridge optimizations. https://github.com/GermanAizek/mongodb-without-avx
Hi, we compile binaries and build images without AVX requirement for our needs. If those artifacts suit you, give it a try. https://github.com/flakybitnet/mongodb-docker
Name and Version
bitnami/mongdb v12.1.3
What steps will reproduce the bug?
test-mongodb-values.yaml just as below
What is the expected behavior?
3 mongodb pods created successfully. It works days before..
What do you see instead?
Additional information
Ubuntu 20.04 TLS Storage Class: nfs-client NFS server ready and mounted on every nodes