Installation of druid using helm not working in AWS (EKS)

I have a 3 node EC2 instance(xlarge) AWS (EKS) cluster and using helm installing the druid but the pods are in CrashLoopBackOff state.

The druid is never coming up and using the default chart values.

Could you please help me out here the reason for failure

command used

$ helm install --namespace “druid” --name “druid” incubator/druid

$ kubectl get pods -n druid

NAME READY STATUS RESTARTS AGE

druid-broker-74769d575f-77lgc 0/1 CrashLoopBackOff 19 95m

druid-coordinator-5c49599bdb-wbd8k 0/1 Running 24 95m

druid-historical-0 0/1 CrashLoopBackOff 16 95m

druid-middle-manager-0 0/1 CrashLoopBackOff 19 95m

druid-mysql-b8f6777f9-8flmx 1/1 Running 0 95m

druid-overlord-577d8d89fb-sp8h9 0/1 CrashLoopBackOff 23 95m

druid-zookeeper-0 1/1 Running 6 34m

druid-zookeeper-1 1/1 Running 0 94m

druid-zookeeper-2 1/1 Running 0 93m

Hi,

Could you provide a sample of your pod logs ?

Two pods describe below.

$ kubectl describe pod druid-middle-manager-0 -n druid
Name: druid-middle-manager-0
Namespace: druid
Priority: 0
PriorityClassName:
Node: ip-192-168-241-130.ec2.internal/192.168.241.130
Start Time: Tue, 11 Jun 2019 22:31:07 +0530
Labels: app=druid
component=middle-manager
controller-revision-hash=druid-middle-manager-6c7f88d76b
release=druid
statefulset.kubernetes.io/pod-name=druid-middle-manager-0
Annotations:
Status: Running
IP: 192.168.201.91
Controlled By: StatefulSet/druid-middle-manager
Containers:
druid:
Container ID: docker://54385b676854d1e8758024ca06bf6eec95a1c07ec00fe42978744f5a63f9dcd7
Image: maver1ckpl/druid-docker:0.12.3-2
Image ID: docker-pullable://maver1ckpl/druid-docker@sha256:1481bbc3ebe6b1a84dc310733d0607f7e6d14607fb813069f56925b0eb4ca3f9
Port: 8091/TCP
Host Port: 0/TCP
Args:
middleManager
State: Running
Started: Tue, 11 Jun 2019 23:13:01 +0530
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Tue, 11 Jun 2019 23:06:57 +0530
Finished: Tue, 11 Jun 2019 23:07:55 +0530
Ready: False
Restart Count: 11
Liveness: http-get http://:8091/status/health delay=60s timeout=1s period=10s #success=1 #failure=3
Readiness: http-get http://:8091/status/health delay=60s timeout=1s period=10s #success=1 #failure=3
Environment:
ZOOKEEPER_HOST: druid-zookeeper-headless:2181
DB_HOST: druid-mysql
DB_TYPE: mysql
DB_USERNAME: druid
DB_PASSWORD: druid
DB_DBNAME: druid
DB_PORT: 3306
JAVA_OPTS: -Xms1G -Xmx1G
DRUID_USE_CONTAINER_IP: true
Mounts:
/var/druid/ from data (rw)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-wbv9p (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-druid-middle-manager-0
ReadOnly: false
default-token-wbv9p:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-wbv9p
Optional: false
QoS Class: BestEffort
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message


Normal Scheduled 42m default-scheduler Successfully assigned druid/druid-middle-manager-0 to ip-192-168-241-130.ec2.internal
Normal SuccessfulAttachVolume 42m attachdetach-controller AttachVolume.Attach succeeded for volume “pvc-ff5075dd-8c09-11e9-827d-0ab0ed1fe82a”
Normal Pulled 37m (x5 over 42m) kubelet, ip-192-168-241-130.ec2.internal Container image “maver1ckpl/druid-docker:0.12.3-2” already present on machine
Normal Created 37m (x5 over 42m) kubelet, ip-192-168-241-130.ec2.internal Created container
Normal Started 37m (x5 over 42m) kubelet, ip-192-168-241-130.ec2.internal Started container