[prev in list] [next in list] [prev in thread] [next in thread] 

List:       solr-user
Subject:    Re: Solr & Kubernetes - how to configure the liveness
From:       戴晓彬 <xiaobin_dai () foxmail ! com>
Date:       2021-10-31 15:14:41
Message-ID: tencent_D3BCB78F1C86EAEE1EDA7DB8CABBB59E7F09 () qq ! com
[Download RAW message or body]

I'm a little puzzled, why UNHEALTHY_STATES does not contain State.RECOVERY_FAILED

> 2021年10月31日 22:45，Jan Høydahl <jan.asf@cominvent.com> 写道：
> 
> See https://solr.apache.org/guide/8_10/implicit-requesthandlers.html#admin-handlers, \
> you can query each node with  
> http://node:8983/api/node/health?requireHealthyCores=true
> 
> It will only return HTTP 200 if all active cores on the node are healthy (none \
> starting or recovering). 
> Jan
> 
> > 27. okt. 2021 kl. 17:27 skrev Vincenzo D'Amore <v.damore@gmail.com>:
> > 
> > Hi all,
> > 
> > when a Solr instance is started I would be sure all the indexes present are
> > up and running, in other words that the instance is healthy.
> > The healthy status (aka liveness/readiness) is especially useful when a
> > Kubernetes SolrCloud cluster has to be restarted for any configuration
> > management needs and you want to apply your change one node at a time.
> > AFAIK I can ping only one index at a time, but there is no way out of the
> > box to test that a bunch of indexes are active (green status).
> > Have you ever faced the same problem? What do you think?
> > 
> > Best regards,
> > Vincenzo
> > 
> > -- 
> > Vincenzo D'Amore
> 


[prev in list] [next in list] [prev in thread] [next in thread]