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

List:       solr-user
Subject:    Re: Enforcing a hard timeout on shard requests?
From:       Jason Hellman <jhellman () innoventsolutions ! com>
Date:       2014-05-30 22:09:00
Message-ID: 6C0571BA-2D9A-4BCA-8BBC-7269596E63FE () innoventsolutions ! com
[Download RAW message or body]

Gregg,

I don’t have an answer to your question but I’m very curious what use case you have \
that permits such arbitrary partial-results.  Is it just an edge case or do you want \
to permit a common occurrence?

Jason

On May 30, 2014, at 3:05 PM, Gregg Donovan <greggny3@gmail.com> wrote:

> I'd like a to add a hard timeout on some of my sharded requests. E.g.: for
> about 30% of the requests, I want to wait no longer than 120ms before a
> response comes back, but aggregating results from as many shards as
> possible in that 120ms.
> 
> My first attempt was to use timeAllowed=120&shards.tolerant=true. This sort
> of works, in that I'll see partial results occasionally, but slow shards
> will still take much longer than my timeout to return, sometimes up to
> 700ms. I imagine if the CPU is busy or the node is GC-ing that it won't be
> able to enforce the timeAllowed and return.
> 
> Is there a way to enforce this timeout without failing the request
> entirely? I'd still like to get as many shards to return in 120ms as I can,
> even if they have partialResults.
> 
> Thanks.
> 
> --Gregg


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