well, we do not use solrcloud, just simple solr deployment - one master with some relicas. I agree with Shawn's opinion, I think we need to upgrade the physical memory, and allocate the reasonable jvm size.
Thank you all the same! Best Regards! Kent 2016-11-02 4:52 GMT+08:00 Erick Erickson <erickerick...@gmail.com>: > This is a bit confusing as you're mixing terms from > older master/slave Solr with SolrCloud. > > You say "our deployment is one master with 10 replicas" > and > "we index data to the > master, and search data from the replicas via load balancing" > > So how are you getting your data to the replicas? > > There is no "master" in SolCloud, just a "leader" whose > role as assumed by one replica for each shard. > > However, if you are issuing a "fetchindex" via > the replication API to move the data to an > independent search cluster, your might be seeing: > > https://issues.apache.org/jira/browse/SOLR-9706 > > --------------- > Now, the only real time I've seen this be necessary > is in _extremely_ heavy indexing situations. Otherwise > you should just have a single solrCloud that you index > to and search from. > > Or do you have some setup where each replica acts > as a slave to some replica in your indexing cluster? I > suspect that runs into the same situation as described > in SOLR-9706. > > In the "normal" case, the only time a replica should > do a fetchindex is when it should be in a "recovering" > state and not be serving any queries anyway. > > ------------ > Again, though, unless it's a rather unusual setup you > shouldn't need to do this. > > Best, > Erick > > On Tue, Nov 1, 2016 at 9:46 AM, Fuad Efendi <f...@efendi.ca> wrote: > > Quote: > > It takes place not often. after analysis, we find that only when the > > replicas Synchronous Data from master solr server. it seem that when the > > replicas block search requests when synchronizing data from master, is > that > > true? > > > > > > Solr makes new searcher available after replication complete, and new > *trivial* searches should take milliseconds of response time even with zero > cache tunings including OS managed caches for filesystem. > > > > However, if first search coming uses faceting (which uses field caches) > then it may takes from seconds to minutes to many minutes just to warm up > internal caches. > > > > Solr has the way to warm up internal caches before making new searcher > available: https://cwiki.apache.org/confluence/display/solr/Query+ > Settings+in+SolrConfig > > > > Make this queries typical for your use cases (for instance, *:* with > faceting): > > > > <listener event="newSearcher" class="solr.QuerySenderListener"> > > <arr name="queries"> > > <!-- > > <lst><str name="q">solr</str><str name="sort">price asc</str></lst> > > <lst><str name="q">rocks</str><str name="sort">weight asc</str></lst> > > --> > > </arr> > > </listener> > > > > > > > > Thanks, > > > > -- > > Fuad Efendi > > (416) 993-2060 > > http://www.tokenizer.ca > > Search Relevancy and Recommender Systems > > > > > > On November 1, 2016 at 12:07:50 PM, Kent Mu (solr.st...@gmail.com) > wrote: > > > > Hi friends! > > We come across an issue when we use the solrj(4.9.1) to connect to solr > > server, our deployment is one master with 10 replicas. we index data to > the > > master, and search data from the replicas via load balancing. > > > > the error stack is as below: > > > > *Timeout occured while waiting response from server at: > > http://review.solrsearch3.cnsuning.com/solr/commodityReview > > <http://review.solrsearch3.cnsuning.com/solr/commodityReview>* > > org.apache.solr.client.solrj.SolrServerException: Timeout occured while > > waiting response from server at: > > http://review.solrsearch3.cnsuning.com/solr/commodityReview > > at > > org.apache.solr.client.solrj.impl.HttpSolrServer. > executeMethod(HttpSolrServer.java:562) > > ~[solr-solrj-4.9.1.jar:4.9.1 1625909 - mike - 2014-09-18 04:09:05] > > at > > org.apache.solr.client.solrj.impl.HttpSolrServer.request( > HttpSolrServer.java:210) > > ~[solr-solrj-4.9.1.jar:4.9.1 1625909 - mike - 2014-09-18 04:09:05] > > at > > org.apache.solr.client.solrj.impl.HttpSolrServer.request( > HttpSolrServer.java:206) > > ~[solr-solrj-4.9.1.jar:4.9.1 1625909 - mike - 2014-09-18 04:09:05] > > at > > org.apache.solr.client.solrj.request.QueryRequest.process( > QueryRequest.java:91) > > ~[solr-solrj-4.9.1.jar:4.9.1 1625909 - mike - 2014-09-18 04:09:05] > > at org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:310) > > ~[solr-solrj-4.9.1.jar:4.9.1 1625909 - mike - 2014-09-18 04:09:05] > > > > It takes place not often. after analysis, we find that only when the > > replicas Synchronous Data from master solr server. it seem that when the > > replicas block search requests when synchronizing data from master, is > that > > true? > > I wonder if it is because that our solr server hardware configuration > > is too low? the physical memory is 8G with 4 cores. and the JVM we set is > > Xms512m, Xmx7168m. > > > > looking forward to your reply. > > > > Thanks! >
