HI @gkafity ,
As it’s testing Env Sys Requirements are kept low, CPU Core is 2 with 16 GB RAM for each node.
What does it means? Sorry but I did’t see this point in system requirements docs, thats why I’m putting below storage config in sdb-cluster.yaml file.
Current storage of Master and worker node are 100GB & 50 GB respectively.
aggregatorSpec: #The height value specifies the vCPU and RAM size of an aggregator or leaf node where a height of 1 equals 8 vCPU cores and 32 GB of RAM.
count: 1 #The smallest value you can set is 0.5 (4 vCPU cores, 16 GB of RAM).
height: 0.5
storageGB: 20 #The storageGB value corresponds to the amount of storage each aggregator or leaf should request for their persistent data volume.
storageClass: standard
objectMetaOverrides:
annotations:
optional: annotation
labels:
optional: label
leafSpec:
count: 1
height: 0.5
storageGB: 20
storageClass: standard
It’s not able to connect.
[root@learning-1 ss_kubernetese]# mysql -u admin -h 10.102.231.87 -P 3306 -p *9177CC8207174BDBB5ED66B2140C75171283F15D
Enter password:
ERROR 2002 (HY000): Can't connect to server on '10.102.231.87' (115)
It already tried and tested, K8s Testing is going on currently.
Linux cluster working now.
Ref link:Leaf Node went offline,How to restart and connect this node to the cluster
Below Error is coming due to storage issue?
Due to which Aggregator and Leaf pods are not spinning or there can be config issue in yaml files.
Let me know if you need any logs,wants this issue to get resolved.
[root@learning-1 ss_kubernetese]# kubectl logs deployment/sdb-operator
2022/10/14 04:42:26 deleg.go:121 {cmd} --cluster-id: sdb-cluster
2022/10/14 04:42:26 deleg.go:121 {cmd} --fs-group-id: 5555
2022/10/14 04:42:26 deleg.go:121 {controller-runtime.metrics} Metrics server is starting to listen addr: "0.0.0.0:9090"
2022/10/14 04:42:26 deleg.go:121 {cmd} starting manager
2022/10/14 04:42:26 logr.go:249 Starting server path: "/metrics" kind: "metrics" addr: "[::]:9090"
I1014 04:42:26.956979 1 leaderelection.go:248] attempting to acquire leader lease default/memsql-operator-lock-sdb-cluster...
I1014 06:35:43.689297 1 leaderelection.go:258] successfully acquired lease default/memsql-operator-lock-sdb-cluster
2022/10/14 06:35:43 logr.go:249 {events} Normal object: "{Kind:ConfigMap Namespace:default Name:memsql-operator-lock-sdb-cluster UID:48580f1d-64b3-4f21-92f4-13d2951357f4 APIVersion:v1 ResourceVersion:20659 FieldPath:}" reason: "LeaderElection" message: "sdb-operator-564b9d7d97-cxjjm_9b57f782-db08-48b4-95a7-59688d3e941f became leader"
2022/10/14 06:35:43 logr.go:249 {events} Normal object: "{Kind:Lease Namespace:default Name:memsql-operator-lock-sdb-cluster UID:7fd4ccbd-dff9-45e1-9941-bc6e03ca138d APIVersion:coordination.k8s.io/v1 ResourceVersion:20660 FieldPath:}" reason: "LeaderElection" message: "sdb-operator-564b9d7d97-cxjjm_9b57f782-db08-48b4-95a7-59688d3e941f became leader"
2022/10/14 06:35:43 logr.go:249 {controller.memsqlcluster} Starting EventSource reconciler kind: "MemsqlCluster" reconciler group: "memsql.com" source: "kind source: *v1alpha1.MemsqlCluster"
2022/10/14 06:35:43 logr.go:249 {controller.memsqlcluster} Starting EventSource reconciler group: "memsql.com" reconciler kind: "MemsqlCluster" source: "kind source: *v1alpha1.MemsqlCluster"
2022/10/14 06:35:43 logr.go:249 {controller.memsqlcluster} Starting EventSource reconciler group: "memsql.com" r econciler kind: "MemsqlCluster" source: "kind source: *v1.StatefulSet"
2022/10/14 06:35:43 logr.go:249 {controller.memsqlcluster} Starting EventSource reconciler kind: "MemsqlCluster" reconciler group: "memsql.com" source: "kind source: *v1.Service"
2022/10/14 06:35:43 logr.go:249 {controller.memsqlcluster} Starting EventSource reconciler kind: "MemsqlCluster" reconciler group: "memsql.com" source: "kind source: *v1.Secret"
2022/10/14 06:35:43 logr.go:249 {controller.memsqlcluster} Starting Controller reconciler group: "memsql.com" reconciler kind: "MemsqlCluster"
2022/10/14 06:35:44 deleg.go:121 {controller.memsql} reconciliation cause: statefulset namespace: "default" clusterName: "sdb-cluster" serviceName: "svc-sdb-cluster" namespace: "default"
2022/10/14 06:35:44 deleg.go:121 {controller.memsql} reconciliation cause: statefulset namespace: "default" clusterName: "sdb-cluster" serviceName: "svc-sdb-cluster-ddl" namespace: "default"
2022/10/14 06:35:44 deleg.go:121 {controller.memsql} reconciliation cause: memsqlcluster clusterName: "sdb-cluster" namespace: "default"
2022/10/14 06:35:44 logr.go:249 {controller.memsqlcluster} Starting workers reconciler group: "memsql.com" reconciler kind: "MemsqlCluster" worker count: "1"
2022/10/14 06:35:44 logr.go:249 {controller.memsql} Reconciling MemSQL Cluster. Request.Namespace: "default" Request.Name: "sdb-cluster"
2022/10/14 06:35:44 deleg.go:121 {memsql} can't find operator deployment, trying uncached client key: "default/operator-sdb-cluster"
2022/10/14 06:35:44 deleg.go:135 {memsql} can't find operator deployment, metrics service will not be created error: "deployments.apps "operator-sdb-cluster" not found"
2022/10/14 06:35:44 deleg.go:135 {controller.memsql} Reconciler error, will retry after 1s: "error" failed to get service endpoint (svc-sdb-cluster-ddl): no ingress endpoint found