search

cetic / helm-nifi

Helm Chart for Apache Nifi
Apache License 2.0
213 stars 220 forks source link

[cetic/nifi] Readiness probe failed #177

Open Okanmercan99 opened 2 years ago

Okanmercan99 commented 2 years ago

Describe the bug When I started celtic/nifi with replicationCount=# > 1, get error "Readiness probe failed: dial tcp 172.17.0.6:8080: connect: connection refused" and pods restarting itself over and over again. I tried to increase initialDelaySeconds up to 240 sec but it not solve the problem.

Version of Helm and Kubernetes: Helm v3.6.3

What happened: Pods restarting themselves and try to connect the service.

How to reproduce it (as minimally and precisely as possible): helm install nifi cetic/nifi --set replicaCount=# > 1

Anything else we need to know: Pods seems running normal, their logs are clear. I think cause of problem is related to service implementation.

pankaj891 commented 1 year ago

Hey , i am deploying this helm in local docker desktop k8s and after installation, 3 pods are created for zookeeper and 1 pod is for nifi instance because i configured replicacount 1 . but in nifi instance pod , one container is continuously restart again & again , i am not able to find why this is happening but when i describe that pod it shows readiness probe failed in events. Can you help me to find out what i have to change in configuration if i am doing something wrong.