aloosnetmatch closed issue #760: Solr -operator and prometheus-exporter
URL: https://github.com/apache/solr-operator/issues/760
--
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.
aloosnetmatch commented on issue #760:
URL: https://github.com/apache/solr-operator/issues/760#issuecomment-2739534445
Hi.
I managed to fix the issue.
The ingress, we tried in the past, we didn't got it to work back then.
So the solr-operator tried to configure the ingress but th
gerlowskija commented on issue #760:
URL: https://github.com/apache/solr-operator/issues/760#issuecomment-2718204202
I spent some time this morning trying to trigger this using the
`release-0.9` branch (Operator 0.9.0, essentially), and Solr 9.8.0, and
couldn't reproduce. Since @aloosnetma
HoustonPutman commented on issue #760:
URL: https://github.com/apache/solr-operator/issues/760#issuecomment-2725179743
@aloosnetmatch can you provide the status of your solrcloud objects as well?
--
This is an automated message from the Apache Git Service.
To respond to the message, please
HoustonPutman commented on issue #760:
URL: https://github.com/apache/solr-operator/issues/760#issuecomment-2725981347
So if you look at those logs, the Solr Operator cannot create an Ingress for
you because your ingress controller is rejecting it. Because of this, the
SolrCloud cannot fini
aloosnetmatch commented on issue #760:
URL: https://github.com/apache/solr-operator/issues/760#issuecomment-2725298847
Here is the solr operator log.
[solr-operator_nonp_logs.txt](https://github.com/user-attachments/files/19251664/solr-operator_nonp_logs.txt)
For which "solrclo
HoustonPutman commented on issue #760:
URL: https://github.com/apache/solr-operator/issues/760#issuecomment-2725209476
Also could you provide your operator logs? The most likely culprit here is
that there is an error in the SolrCloud reconciling and it cannot set its
status.
--
This is a
gerlowskija commented on issue #760:
URL: https://github.com/apache/solr-operator/issues/760#issuecomment-2725116667
@aloosnetmatch - is this a transient error that goes away as the
operator/pods retry, or does the error keep happening once it arises?
Assuming it's transient, I could
aloosnetmatch commented on issue #760:
URL: https://github.com/apache/solr-operator/issues/760#issuecomment-2724592639
Thanks for your reply.
I looked up the requested info:
This time I compared the PROD environment ( which runs solr operator 0.8.1
and solr 9.7.0)
to the NO
HoustonPutman commented on issue #760:
URL: https://github.com/apache/solr-operator/issues/760#issuecomment-2722006358
Yeah, the only way for `ZK_HOST` to not actually have a value is to do some
really weird stuff, so it would be necessary to see what your `solrcloud` and
`solrprometheusexp
aloosnetmatch opened a new issue, #760:
URL: https://github.com/apache/solr-operator/issues/760
We upgraded out test env from solr-operator 0.8.1 to 0.9.0 and from solr
9.7.0 to 9.8.0.
The prometheus exporter does not seem to work anymore.
The logging tells me this:
`ERR
11 matches
Mail list logo
