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 <atitaar...@gmail.com> wrote: > 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 : My collection names are prefixed with clientId. > > Thanks, > Atita > > On Feb 1, 2018 10:06 PM, "Erick Erickson" <erickerick...@gmail.com> wrote: > >> 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 shutting down. So you also have to check >> whether the replica's node is in the "live_nodes" znode. >> >> Best, >> Erick >> >> On Thu, Feb 1, 2018 at 4:34 AM, Daniel Carrasco <d.carra...@i2tic.com> >> wrote: >> > 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 >> only >> > if is healthy or recovering?. Of course if is dead I've got no response, >> so >> > that's easy. >> > >> > Thanks and greetings!! >> > >> > -- >> > _________________________________________ >> > >> > Daniel Carrasco Marín >> > Ingeniería para la Innovación i2TIC, S.L. >> > Tlf: +34 911 12 32 84 Ext: 223 >> > www.i2tic.com >> > _________________________________________ >>
