With Azure and also some internal deployments, `nodepool status` takes
more than 3 seconds (it can go up to 6 seconds) and so cassandra is not
coming up or quite randomly.
This patch gives more room to `nodepool status` to answer.
Issue-ID: OOM-2687
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
Change-Id: I98b0adc751e3cd4fa8710f88567cd8896db548eb
# probe configuration parameters
liveness:
initialDelaySeconds: 60
- periodSeconds: 10
- timeoutSeconds: 3
+ periodSeconds: 20
+ timeoutSeconds: 10
successThreshold: 1
failureThreshold: 3
# necessary to disable liveness probe when setting breakpoints
readiness:
initialDelaySeconds: 120
- periodSeconds: 10
- timeoutSeconds: 3
+ periodSeconds: 20
+ timeoutSeconds: 10
successThreshold: 1
failureThreshold: 3