-
Notifications
You must be signed in to change notification settings - Fork 69
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
mayastor addon issue #44
Comments
inspection-report-20220505_064430.tar.gz |
Hi @balasu, I see this:
Could you add more cores to this VM or provide a second node on the cluster? |
Hi with more cores it works, however |
The addon should point the interested users to the official docs. Mayastore can't be deployed on small clusters. It has high hardware resource requirements and works only with dedicated disks. It is not intended to replace Jiva or Cstor, which do have acceptable low hardware requirements. Out of this discussion, but Mayastore is a component which does not fit the idea of small, like MicroK8s intends to promote, it is the total opposite. To make a small understanding: Mayastore wants for itself minimum 2 cpu cores and 4GB of ram. So, to run only Mayastore and some low requirements application, a cluster with minimum 3-4 cpu cores and 6-8gb or ram is the critical minimum hardware requirements, multiplied by 3 workers, each one with dedicated disks for Mayastore. Simply having the addon enabled, will also not provide any benefits. |
Hi
I installed microk8s 1.24 on a single node vm Ubuntu 21.10 .microk8s enable mayastor command enables storage classes mayastor and mayastor-3, however default storage class annotation is not set for any 1 of them, so I set for mayastor with
default storage class annotation
however mayastor pod is still in pending state
pl suggest no error ,also requesting set atleast mayastor storageclass as default
The text was updated successfully, but these errors were encountered: