I remembered why we waited for 6.5.1. It is the object leak in the Zookeeper client code. A very slow leak, but worth getting a fix.
I tested our cluster at 6000 requests/minute. It is 18 million documents, four shards by four replicas on big AWS instances (c4.8xlarge). We have very long free text queries. Students enter queries with hundreds of words (copy/paste), but we truncate at 40 terms. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On May 24, 2017, at 12:33 PM, Nawab Zada Asad Iqbal <khi...@gmail.com> wrote: > > Thanks everyone for the responses, I will go with the latest bits for now; > and will share how it goes. > > @Toke, I stumbled upon your page last week but it seems that your huge > index doesn't receive a lot of query traffic. Mine is around 60TB and > receives around 120 queries per second; ~90 shards on 30 machines. > > > I look forward to hear more scale stories. > Nawab > > On Wed, May 24, 2017 at 7:58 AM, Toke Eskildsen <t...@kb.dk> wrote: > >> Shawn Heisey <apa...@elyograg.org> wrote: >>> On 5/24/2017 3:44 AM, Toke Eskildsen wrote: >>>> It is relatively easy to downgrade to an earlier release within the >>>> same major version. We have not switched to 6.5.1 simply because we >>>> have no pressing need for it - Solr 6.3 works well for us. >> >>> That strikes me as a little bit dangerous, unless your indexes are very >>> static. The Lucene index format does occasionally change in minor >>> versions. >> >> Err.. Okay? Thank you for that. I was under the impression that the index >> format was fixed (modulo critical bugs) for major versions. This will >> change our approach to updating. >> >> Apologies for the confusion, >> Toke >>
