[GitHub] [solr-operator] mmoscher commented on issue #477: Support Zookeeper `probes` parameters in Apache Solr Operator helm charts.

2022-10-25 Thread GitBox
mmoscher commented on issue #477: URL: https://github.com/apache/solr-operator/issues/477#issuecomment-1290888915 @iampranabroy yes, all resources (Solr + ZK) in the same namespace with NetworkPolicies denying all pod's egress traffic. -- This is an automated message from the Apache Git

[GitHub] [solr-operator] mmoscher commented on issue #477: Support Zookeeper `probes` parameters in Apache Solr Operator helm charts.

2022-10-25 Thread GitBox
mmoscher commented on issue #477: URL: https://github.com/apache/solr-operator/issues/477#issuecomment-1290422940 @HoustonPutman yes, solved it without using any probes. The problem was related to wrong NetworkPolicies and old (maybe corrupted) configs in the zookeeper PVC, cf.

[GitHub] [solr-operator] mmoscher commented on issue #477: Support Zookeeper `probes` parameters in Apache Solr Operator helm charts.

2022-09-26 Thread GitBox
mmoscher commented on issue #477: URL: https://github.com/apache/solr-operator/issues/477#issuecomment-1258145043 However, can confirm that the described solutions, i.e. increasing the livenessProbe.initialDelaySeconds, works. Setting this to 30s I was able to successfully deploy a

[GitHub] [solr-operator] mmoscher commented on issue #477: Support Zookeeper `probes` parameters in Apache Solr Operator helm charts.

2022-09-26 Thread GitBox
mmoscher commented on issue #477: URL: https://github.com/apache/solr-operator/issues/477#issuecomment-1258126365 @iampranabroy did you found an interim solution? Facing the same issue and I think (for now) the only way to go is to deploy an separated zookeeper cluster. Will dig