timeAllowed is not a realtime (as well as java per se). There is only a few places which it can break.
On Wed, Aug 22, 2018 at 4:09 PM Ash Ramesh <ash...@canva.com> wrote: > Hi again, > > Specs: 7.3.1 | 8 Shards | Solr Cloud > > I was wondering how the timeAllowed parameter works when you architect your > cluster in a sharded and distributed manner. This is the curl command and > the timing > > Query: > > http://localhost:9983/solr/media/select?fq=someField:someRedactedValue&q=*:*&qq=*&rows=10&start=400000&timeAllowed=5000 > < > http://localhost:9983/solr/media/select/images?fq=brand:BACsIfMoQVQ&q=*:*&qq=*&rows=10&start=400000&timeAllowed=5000 > > > Time: 14.16 sec > > The request actually returns results, which apparently is expected, but why > does it not timeout? I've grepped the internet to understand this, but > still haven't gotten a full explanation. I inferred that the behaviour is > different between a single sharded cluster and multi sharded cluster. > > Best Regards, > > Ash > > -- > *P.S. We've launched a new blog to share the latest ideas and case studies > from our team. Check it out here: product.canva.com > <http://product.canva.com/>. *** > ** <https://canva.com>Empowering the world > to design > Also, we're hiring. Apply here! > <https://about.canva.com/careers/> > <https://twitter.com/canva> > <https://facebook.com/canva> <https://au.linkedin.com/company/canva> > <https://instagram.com/canva> > > > > > > -- Sincerely yours Mikhail Khludnev
