liveness and rediness probe configuration for Ignite on kubernetes

classic Classic list List threaded Threaded
2 messages Options
shivakumar shivakumar
Reply | Threaded
Open this post in threaded view
|

liveness and rediness probe configuration for Ignite on kubernetes

Hi all,
I have deployed Ignite on Kubernetes and configured liveness and readiness probe like this 
        readinessProbe:
          tcpSocket:
            port: 10800
          initialDelaySeconds: 10
          periodSeconds: 2
          failureThreshold: 60
        livenessProbe:
          httpGet:
           scheme: HTTP
           path: /ignite?cmd=version&user=ignite&password=ignite
           port: 8080
          initialDelaySeconds: 60
          periodSeconds: 20

where 10800 is SQL port and 8080 is rest port.

The problem I am facing here is, If pod restarts for some reason then liveness probe is failing because during recovery of Ignite node(pod) it is failing to respond to rest API (liveness probe) and this leads to again restart by Kubernetes and pod going into crashLoopBackOff state.

Is there any other best way of configuring liveness probe?
during recovery of Ignite node, why it is failing to respond to a simple rest API query ( /ignite?cmd=version ) ?

regards,
shiva
 

M. Ilya M. Ilya
Reply | Threaded
Open this post in threaded view
|

RE: liveness and rediness probe configuration for Ignite on kubernetes

Hi Shiva,

Could you please check that ignite-rest-http library is added to OPTION_LIBS environment parameter, i.e.:
      containers:
      - name: ignite
        image: apacheignite/ignite:2.6.0
        env:
        - name: OPTION_LIBS
          value: ignite-kubernetes,ignite-rest-http

If this library is present in OPTION_LIBS can you share your StatefulSet/Deployment configuration template?

Thank you,
Ilya.

От: Shiva Kumar <[hidden email]>
Отправлено: 18 сентября 2019 г. 11:07
Кому: [hidden email] <[hidden email]>
Тема: liveness and rediness probe configuration for Ignite on kubernetes
 
Hi all,
I have deployed Ignite on Kubernetes and configured liveness and readiness probe like this 
        readinessProbe:
          tcpSocket:
            port: 10800
          initialDelaySeconds: 10
          periodSeconds: 2
          failureThreshold: 60
        livenessProbe:
          httpGet:
           scheme: HTTP
           path: /ignite?cmd=version&user=ignite&password=ignite
           port: 8080
          initialDelaySeconds: 60
          periodSeconds: 20

where 10800 is SQL port and 8080 is rest port.

The problem I am facing here is, If pod restarts for some reason then liveness probe is failing because during recovery of Ignite node(pod) it is failing to respond to rest API (liveness probe) and this leads to again restart by Kubernetes and pod going into crashLoopBackOff state.

Is there any other best way of configuring liveness probe?
during recovery of Ignite node, why it is failing to respond to a simple rest API query ( /ignite?cmd=version ) ?

regards,
shiva