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

mayastor addon issue #44

Open
balasu opened this issue May 5, 2022 · 4 comments
Open

mayastor addon issue #44

balasu opened this issue May 5, 2022 · 4 comments

Comments

@balasu
Copy link
Collaborator

balasu commented May 5, 2022

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

root@localhost:~# microk8s kubectl patch storageclass mayastor -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
storageclass.storage.k8s.io/mayastor patched

however mayastor pod is still in pending state

root@localhost:~# microk8s kubectl get po -n mayastor
NAME                                      READY   STATUS    RESTARTS   AGE
mayastor-csi-cwxpv                        0/2     Pending   0          31m
etcd-operator-mayastor-6b97bdb8dc-76qd6   1/1     Running   0          31m
etcd-4f8hh964ck                           1/1     Running   0          31m
core-agents-d6487674f-5qjsk               1/1     Running   0          31m
msp-operator-d47945d87-z2t7h              1/1     Running   0          31m
rest-754bb6c7f8-9c5tz                     1/1     Running   0          31m
mayastor-qvx8q                            1/1     Running   0          31m
csi-controller-5dd6f68f45-xm24g           3/3     Running   0          31m

pl suggest no error ,also requesting set atleast mayastor storageclass as default

@balasu
Copy link
Collaborator Author

balasu commented May 5, 2022

inspection-report-20220505_064430.tar.gz
pl find inspect logs

@ktsakalozos
Copy link
Member

Hi @balasu,

I see this:

"0/1 nodes are available: 1 Insufficient cpu. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod."

Could you add more cores to this VM or provide a second node on the cluster?

@balasu
Copy link
Collaborator Author

balasu commented May 5, 2022

Hi with more cores it works, however microk8s enable portainer --storage-addon=mayastor to work , default storage class annotation is required else user have to do microk8s enable mayastor and patch annotation '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}' and microk8s enable portainer --storage-class=mayastor.

@madalinignisca
Copy link

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.

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

No branches or pull requests

3 participants