Re: TimeoutException, IOException, Read timed out

I am happy to report that <1> fixed these: PERFORMANCE WARNING: Overlapping onDeckSearchers=2 We still occasionnally see timeouts so we may have to explore <2>. On Thu, Oct 26, 2017 at 12:12 PM, Fengtan wrote: > Thanks Erick and Emir -- we are going to start with <1> and possibly <2>. > >

Re: TimeoutException, IOException, Read timed out

Thanks Erick and Emir -- we are going to start with <1> and possibly <2>. On Thu, Oct 26, 2017 at 7:06 AM, Emir Arnautović < emir.arnauto...@sematext.com> wrote: > Hi Fengtan, > I would just add that when merging collections, you might want to use > document routing (https://lucene.apache.org/sol

Re: TimeoutException, IOException, Read timed out

Hi Fengtan, I would just add that when merging collections, you might want to use document routing (https://lucene.apache.org/solr/guide/6_6/shards-and-indexing-data-in-solrcloud.html#ShardsandIndexingDatainSolrCloud-DocumentRouting

Re: TimeoutException, IOException, Read timed out

<1> It's not the explicit commits are expensive, it's that they happen too fast. An explicit commit and an internal autocommit have exactly the same cost. Your "overlapping ondeck searchers" is definitely an indication that your commits are happening from somwhere too quickly and are piling up. <