We are going to production in a couple of weeks and up to now we haven't
experiment any index corruption during our development. I was asking that
because our SLA requires high availability and I want to make sure that we
can react quickly if corruption occurs. I think I'll go ahead with a
/admin/ping periodically called from the load balancer. Should be ok.
Thanks.
On Fri, May 10, 2013 at 9:10 AM, Erik Hatcher <erik.hatc...@gmail.com>wrote:
> Would a non-successful /select?q={!cache=false}*:* query be sufficient?
> (if so, /admin/ping would do the trick) What's causing index corruption
> in your environment? That's a very unusual occurrence that would be good
> to have identified in gory detail if you can.
>
> Erik
>
> On May 7, 2013, at 20:04 , Michel Dion wrote:
>
> > Hello,
> >
> > I'm look for a way to detect solr index corruption using a http get
> > command. I've look at the /admin/ping and /admin/luke request handlers
> but
> > not sure if the their status provide guarantees that everything is all
> > right. The idea is to be able to tell a load balancer to put a given solr
> > instance out of rotation if its index is corrupted.
> >
> > Thanks
> >
> > Michel
>
>
