brickpattern opened a new issue, #620:
URL: https://github.com/apache/solr-operator/issues/620
**Issue:** Endpoints /admin/ping get 404
**Setup:**
Solr Operator : v0.7.1
ZK: in-built ZK along with Solr Operator
Solr Cloud: v9.x
All modules running in same namespace Solr and Pods all mapped to specific
K8S Node via podOptions ( Tolerations ).
Solr Prometheus Exporter was deployed after the above setup was working
independantly.
**Startup Error:**
```
INFO - 2023-09-12 16:03:01.295;
org.apache.solr.common.cloud.ConnectionManager; Client is connected to ZooKeeper
WARN - 2023-09-12 16:03:01.295; org.apache.solr.common.cloud.SolrZkClient;
Using default ZkACLProvider. DefaultZkACLProvider is not secure, it creates
'OPEN_ACL_UNSAFE' ACLs to Zookeeper nodes
INFO - 2023-09-12 16:03:01.305; org.apache.solr.common.cloud.ZkStateReader;
Updated live nodes from ZooKeeper... (0) -> (3)
INFO - 2023-09-12 16:03:01.325;
org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider; Cluster at
solr-solrcloud-zookeeper-0.solr-solrcloud-zookeeper-headless.solr.svc.cluster.local:2181,solr-solrcloud-zookeeper-1.solr-solrcloud-zookeeper-headless.solr.svc.cluster.local:2181,solr-solrcloud-zookeeper-2.solr-solrcloud-zookeeper-headless.solr.svc.cluster.local:2181
ready
INFO - 2023-09-12 16:03:01.337;
org.apache.solr.prometheus.exporter.SolrExporter; Starting Solr Prometheus
Exporting on port 8080
INFO - 2023-09-12 16:03:01.338;
org.apache.solr.prometheus.collector.SchedulerMetricsCollector; Beginning
metrics collection
INFO - 2023-09-12 16:03:01.354;
org.apache.solr.prometheus.exporter.SolrExporter; Solr Prometheus Exporter is
running. Collecting metrics for cluster f0bf8c7193: Solr Cloud ZK:
solr-solrcloud-zookeeper-0.solr-solrcloud-zookeeper-headless.solr.svc.cluster.local:2181,solr-solrcloud-zookeeper-1.solr-solrcloud-zookeeper-headless.solr.svc.cluster.local:2181,solr-solrcloud-zookeeper-2.solr-solrcloud-zookeeper-headless.solr.svc.cluster.local:2181/
INFO - 2023-09-12 16:03:01.500;
org.apache.solr.client.solrj.impl.CloudSolrClient; request was not
communication error it seems
INFO - 2023-09-12 16:03:01.500;
org.apache.solr.client.solrj.impl.CloudSolrClient; Request to collection
[my.collection] failed due to (500)
org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException: Error
from server at null: null
request: GET, retry=0 maxRetries=5 commError=false errorCode=500
ERROR - 2023-09-12 16:03:01.500;
org.apache.solr.prometheus.scraper.SolrScraper; failed to request: /admin/ping
=> org.apache.solr.client.solrj.SolrServerException: No live SolrServers
available to handle this request
at
org.apache.solr.client.solrj.impl.LBSolrClient$ServerIterator.nextOrError(LBSolrClient.java:220)
org.apache.solr.client.solrj.SolrServerException: No live SolrServers
available to handle this request
at
org.apache.solr.client.solrj.impl.LBSolrClient$ServerIterator.nextOrError(LBSolrClient.java:220)
~[solr-solrj-9.2.1.jar:9.2.1 a4c64ab6a2a270ca69c28c706dabb2927ed8a7c2 -
jsweeney - 2023-04-24 11:35:31]
...
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
~[?:?]
at java.lang.Thread.run(Unknown Source) [?:?]
Caused by:
org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException: Error
from server at null: null
```
Further down in the error list able to see
`org.apache.solr.client.solrj.impl.BaseHttpSolrClient$RemoteSolrException:
Error from server at http://solr-solrcloud-0.solr:80/solr: null
`
Questions :
[ ] - Is the /admin/ping its hitting is to Solr Cloud instance (and not to
ZK instance)? Dont see a domain prefix.
[ ] - Is /admin/ping endpoint request independant of
http://solr-solrcloud-0.solr:80/solr ?
[ ] - Why is it attempting to hit the http://solr-solrcloud-0.solr:80/solr
which happens to be a collections endpoint?
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
