Re: Request node status independently

There's no wildcard for the CLUSTERSTATUS command. You can request status for specific _collections_ by using the "collection" parameter though. Best, Erick On Thu, Feb 1, 2018 at 10:15 AM, Atita Arora wrote: > Hi Erick, > > Just as you mentioned about clusterstatus, I am

Re: Request node status independently

Hi Erick, Just as you mentioned about clusterstatus, I am using the same for almost the similar Usecase. The only issue I run into is that I need some way I could use prefix with collection param, is there some way to do that? So that I can query the specific collection of my interest. Note :

Re: Request node status independently

Thanks to both. Finally I've found a way to do it with haproxy. I do what wunder said sending the command for every collection and see if it's able to answer. Even in recovering answer, so looks like it takes the data from other nodes of use the data that have. Greetings!! El 1 feb. 2018

Re: Request node status independently

Also, “recovering” is a status for a particular core in a collection. A Solr process might have some cores that are healthy and some that are not. Even if you only have one collection, you can still have multiple cores (with different status) from the same collection on one node. Personally, I

Re: Request node status independently

The Collections API CLUSTERSTATUS essentially gives you back the ZK state.json for individual collections (or your cluster, see the params). One note: Just because the state.json reports a replica as "active" isn't definitive. If the node died unexpectedly its replicas can't set the state when

Request node status independently

Hello, I'm trying to create a load balancer using HAProxy to detect nodes that are down or recovering, but I'm not able to find the way to detect if the node is healthy (the only commands i've seen check the entire cluster). Is there any way to check the node status using http responses and get