You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2022/07/27 01:46:45 UTC

[GitHub] [couchdb-helm] colearendt commented on issue #90: Coordinator node regularly restarts in 3 node cluster

colearendt commented on issue #90:
URL: https://github.com/apache/couchdb-helm/issues/90#issuecomment-1196175525

   Woops - apologies for never responding here. I must admit that I am not super familiar with the internals of couchdb - I would definitely recommend turning off `livenessProbe` though. If the `readinessProbe` fails, that is fine - traffic may not get routed to the pod briefly, but the pod stays alive. Moreover, you can increase `failureThreshold` or increase `periodSeconds` or increase `timeoutSeconds` to make it check more often / allow for more variance.
   
   `livenessProbe` should only be used when "the best thing to do for the service is to kill it." I highly doubt that that is the case if it responds a smidge slowly on occasion (during a sync or some such).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@couchdb.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org