Zookeeper liveness and readiness probes continuously give failed warnings

[Joshuaariolu]

Hi, I'm currently running Solrcloud with zookeeper ensemble and I keep getting the below recurring errors for my liveness and readiness probes.
Not sure why I keep these but I was wondering if anyone else was facing this same issue and how to resolve this?

Warning Unhealthy 2m31s kubelet Liveness probe failed: + source /conf/env.sh
++ DOMAIN=solr-solrcloud-zookeeper-headless.ivz-5338-solr-ns.svc.cluster.local
++ QUORUM_PORT=2888
++ LEADER_PORT=3888
++ CLIENT_HOST=solr-solrcloud-zookeeper-client
++ CLIENT_PORT=2181
++ ADMIN_SERVER_HOST=solr-solrcloud-zookeeper-admin-server
++ ADMIN_SERVER_PORT=8080
++ CLUSTER_NAME=solr-solrcloud-zookeeper
++ CLUSTER_SIZE=3
++ echo ruok
++ nc 127.0.0.1 2181

• OK=
• [[ '' == \i\m\o\k ]]
• exit 1

Readiness probe failed: Zookeeper service is not available for requests + source /conf/env.sh
++ DOMAIN=solr-solrcloud-zookeeper-headless.ivz-5338-solr-ns.svc.cluster.local
++ QUORUM_PORT=2888 ++ LEADER_PORT=3888
++ CLIENT_HOST=solr-solrcloud-zookeeper-client
++ CLIENT_PORT=2181
++ ADMIN_SERVER_HOST=solr-solrcloud-zookeeper-admin-server
++ ADMIN_SERVER_PORT=8080 ++ CLUSTER_NAME=solr-solrcloud-zookeeper
++ CLUSTER_SIZE=3 + source /usr/local/bin/zookeeperFunctions.sh ++ set -ex ++ hostname -s + HOST=solr-solrcloud-zookeeper-0 + DATA_DIR=/data + MYID_FILE=/data/myid + LOG4J_CONF=/conf/log4j-quiet.properties + STATIC_CONFIG=/data/conf/zoo.cfg ++ echo ruok ++ nc 127.0.0.1 2181 + OK= + [[ '' == \i\m\o\k ]] + echo 'Zookeeper service is not available for requests' + exit 1

When I describe the zookeeper pod, the below shows the default values for the readiness and liveness probes.
Ready: True
Restart Count: 0
Liveness: exec [zookeeperLive.sh] delay=10s timeout=1s period=10s #success=1 #failure=3
Readiness: exec [zookeeperReady.sh] delay=10s timeout=10s period=10s #success=1 #failure=3
Environment:

Thanks

[nervo]

@Joshuaariolu isn't it timeout=10s for liveness probe ? It's what we have here as default.