Open vipul-06 opened 1 year ago
Can you try with the most recent Solr Operator version? (v0.6.0
)
It might be an issue that has already been fixed.
Other than that I would recommend only using the parts of the values.yaml file that you care about. Otherwise the defaults will become stale with new versions and its hard to tell what you are overriding.
Ok let me give a try
Ok @HoustonPutman my exporter is now showing running in the logs as previous error seems to be solved but my pod is getting restart and crashLoopbackoff
` INFO - 2022-12-26 10:52:55.121; org.apache.solr.common.cloud.ConnectionManager; Waiting for client to connect to ZooKeeper INFO - 2022-12-26 10:52:55.160; org.apache.solr.common.cloud.ConnectionManager; zkClient has connected INFO - 2022-12-26 10:52:55.160; org.apache.solr.common.cloud.ConnectionManager; Client is connected to ZooKeeper INFO - 2022-12-26 10:52:55.172; org.apache.solr.common.cloud.ZkStateReader; Updated live nodes from ZooKeeper... (0) -> (5) INFO - 2022-12-26 10:52:55.192; org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider; Cluster at my-solr-solrcloud-zookeeper-0.my-solr-new-solrcloud-zookeeper-headless.dev-backend.svc.cluster.local:2181,my-solr-new-solrcloud-zookeeper-1.my-solr-new-solrcloud-zookeeper-headless.dev-backend.svc.cluster.local:2181,my-solr-new-solrcloud-zookeeper-2.my-solr-new-solrcloud-zookeeper-headless.dev-backend.svc.cluster.local:2181,my-solr-new-solrcloud-zookeeper-3.my-solr-new-solrcloud-zookeeper-headless.dev-backend.svc.cluster.local:2181,my-solr-new-solrcloud-zookeeper-4.my-solr-new-solrcloud-zookeeper-headless.dev-backend.svc.cluster.local:2181 ready INFO - 2022-12-26 10:52:55.206; org.apache.solr.prometheus.exporter.SolrExporter; Starting Solr Prometheus Exporting INFO - 2022-12-26 10:52:55.208; org.apache.solr.prometheus.collector.SchedulerMetricsCollector; Beginning metrics collection INFO - 2022-12-26 10:52:55.231; org.apache.solr.prometheus.exporter.SolrExporter; Solr Prometheus Exporter is running
` NAME READY STATUS RESTARTS dev-prom-exporter-solr-metrics-65577bfcc5-s6d2b 1/1 Running 6 (2m11s ago)
As there is nothing in the logs how can I find what is the issue regarding this?
@vipul-06 did you ever get a resolution to this? I'm experiencing the exact same issue in your latest update...everything seems to be working but ultimately a crashloopbackoff.
@HoustonPutman @vipul-06 Any tips on how to stop the metrics pod from crashing? We upgraded Solr Operator to 0.8.1 as there was a fix listed for the Promethius exporter, but that did not seem to help.
Just following up to this; it looks like my issue was caused by starving the exporter of compute resources. Upped to 2vcpu/4GB memory and things worked fine with 0.8.1. My guess is the readiness probe was triggering before the slow CPU-based initial gathering of metrics had completed.
I have deployed solr cloud using helm in gke cluster, below are the steps for deploying which I used
(1) helm repo add apache-solr https://solr.apache.org/charts
(2) kubectl create -f https://solr.apache.org/operator/downloads/crds/v0.5.1/all-with-dependencies.yaml
(3) helm install -n dev-backend solr-operator apache-solr/solr-operator --version 0.5.1
(4)helm install -n dev-backend experro-solr apache-solr/solr -f values-solr.yaml --version=0.5.1 (below is the values-solr.yaml file)
I have enabled basic authentication for my solr cloud and disabled solr exporter
Now I have deployed solr exporter using yaml and not helm for monitoring purpose
The issue I am facing is my exporter pod is giving error of auth failure and is getting crashloopbackoff
Below is my solr exporter yaml which I used
The exporter pod logs are like this
The exporter pod is not able to authenticate and also getting CrashLoopBackoff errors