Hi
I’m trying to get Zeebe to run on Docker Desktop for Windows Kubernetes and seem to be having trouble getting the Zeebe pods and ElasticSearch pods to start running successfully.
I have a yaml file to override some of the parameters as I was running into “Insufficient CPU” and “Insufficient Memory” errors, but they seem to be resolved now. Below are the commands I have run with the respective output.
The linux VM used by Docker has been allocated 6GB RAM and 4 Cores.
I have also reduced the number of replicas to 1, just to keep things simple.
Any idea what the issue could be?
Thanks
Andy
Steps:
[Run]
helm install zeebe zeebe/zeebe-cluster -f local-override-values.yaml
[local-overrider-values.yaml]
resources:
requests:
cpu: “100m”
memory: “512m”
limits:
cpu: “1000m”
memory: “1024m”
pvcSize: “100m”
JavaOpts: |
-XX:+UseParallelGC
-XX:MinHeapFreeRatio=5
-XX:MaxHeapFreeRatio=10
-XX:MaxRAMPercentage=25.0
-XX:GCTimeRatio=4
-XX:AdaptiveSizePolicyWeight=90
-XX:+PrintFlagsFinal
-Xmx256m
-Xms265m
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/usr/local/zeebe/data
-XX:ErrorFile=/usr/local/zeebe/data/zeebe_error%p.log
clusterSize: “1”
partitionCount: “1”
replicationFactor: “1”
cpuThreadCount: “1”
ioThreadCount: “1”
elasticsearch:
imageTag: 6.8.3
resources:
requests:
cpu: “100m”
memory: “512m”
limits:
cpu: “1000m”
memory: “1024m”
volumeClaimTemplate:
accessModes: [ “ReadWriteOnce” ]
storageClassName: “standard”
resources:
requests:
storage: “100m”
replicas: “1”
esJavaOpts: “-Xmx256m -Xms256m”
clusterHealthCheckParams: “wait_for_status=yellow&timeout=1s”
[Run]
kubectl get pods
NAME READY STATUS RESTARTS AGE
elasticsearch-master-0 0/1 Pending 0 23m
zeebe-zeebe-0 0/1 ContainerCreating 0 23m
[Run]
kubectl describe pod zeebe-zeebe-0
Name: zeebe-zeebe-0
Namespace: default
Priority: 0
Node: docker-desktop/192.168.65.3
Start Time: Fri, 24 Jan 2020 22:40:53 +0000
Labels: app=zeebe-zeebe
app.kubernetes.io/instance=zeebe
app.kubernetes.io/name=zeebe-cluster
controller-revision-hash=zeebe-zeebe-7f9f9b7fd8
statefulset.kubernetes.io/pod-name=zeebe-zeebe-0
Annotations:
Status: Pending
IP:
Controlled By: StatefulSet/zeebe-zeebe
Containers:
zeebe-cluster:
Container ID:
Image: camunda/zeebe:0.22.1
Image ID:
Ports: 9600/TCP, 26500/TCP, 26501/TCP, 26502/TCP
Host Ports: 0/TCP, 0/TCP, 0/TCP, 0/TCP
State: Waiting
Reason: ContainerCreating
Ready: False
Restart Count: 0
Limits:
cpu: 1
memory: 1024m
Requests:
cpu: 100m
memory: 512m
Readiness: http-get http://:9600/ready delay=0s timeout=1s period=10s #success=1 #failure=3
Environment:
ZEEBE_LOG_LEVEL: debug
ZEEBE_PARTITIONS_COUNT: 1
ZEEBE_CLUSTER_SIZE: 1
ZEEBE_REPLICATION_FACTOR: 1
JAVA_TOOL_OPTIONS: -XX:+UseParallelGC
-XX:MinHeapFreeRatio=5
-XX:MaxHeapFreeRatio=10
-XX:MaxRAMPercentage=25.0
-XX:GCTimeRatio=4
-XX:AdaptiveSizePolicyWeight=90
-XX:+PrintFlagsFinal
-Xmx256m
-Xms265m
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/usr/local/zeebe/data
-XX:ErrorFile=/usr/local/zeebe/data/zeebe_error%p.log
Mounts:
/usr/local/bin/startup.sh from config (rw,path="startup.sh")
/usr/local/zeebe/conf/zeebe.cfg.toml from config (rw,path="zeebe.cfg.toml")
/usr/local/zeebe/data from data (rw)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-8gwmn (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
data:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: data-zeebe-zeebe-0
config:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: zeebe-zeebe
Optional: false
default-token-8gwmn:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-8gwmn
Optional: false
QoS Class: Burstable
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
Warning FailedScheduling 12m (x2 over 12m) default-scheduler pod has unbound immediate PersistentVolumeClaims
Normal Scheduled 12m default-scheduler Successfully assigned default/zeebe-zeebe-0 to docker-desktop
Warning FailedCreatePodSandBox 12m (x13 over 12m) kubelet, docker-desktop Failed create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod “zeebe-zeebe-0”: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused “process_linux.go:319: getting the final child’s pid from pipe caused “read init-p: connection reset by peer””: unknown
Normal SandboxChanged 2m13s (x559 over 12m) kubelet, docker-desktop Pod sandbox changed, it will be killed and re-created.
[Run]
docker version
Client: Docker Engine - Community
Version: 19.03.5
API version: 1.40
Go version: go1.12.12
Git commit: 633a0ea
Built: Wed Nov 13 07:22:37 2019
OS/Arch: windows/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.5
API version: 1.40 (minimum version 1.12)
Go version: go1.12.12
Git commit: 633a0ea
Built: Wed Nov 13 07:29:19 2019
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.2.10
GitCommit: b34a5c8af56e510852c35414db4c1f4fa6172339
runc:
Version: 1.0.0-rc8+dev
GitCommit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
docker-init:
Version: 0.18.0
GitCommit: fec3683
Kubernetes:
Version: v1.15.5
StackAPI: v1beta2