Hi Erick,
Thanks for your advice about having openSearcher set to true
unnecessary for my case. For CorruptIndexException issue, I think Solr
should handle this quite well too. Because I always shutdown tomcat
gracefully.
Recently I did a couple of tests about this issue. When
Hi team,
Currently I am using Solr 4.10 in tomcat. I have a one shard Solr
Cloud with 3 replicas. I set heap size to 15GB for each node. As I have big
data volume and large amount of query request. So always meet frequent full
GC issue. We have checked this and found that many memory was
Hi Walter, Shawn,
Thanks for your quickly reply, the information you provide is really
helpful. Now I know how to find a right way to resolve my issue.
Regards,
Geng, Wei
--
View this message in context:
I am not mean my Zookeeper cluster is rebooting frequently, just want to
ensure my query service can be stable when Zookeeper cluster has issue or
reboot. Will do some test to check if there is some issue here. Maybe
current Zookeeper client can handle this case well. Hacking the client will
Hi Shawn,
Thanks for your detail explanation. The reason I want to shutdown
the CloudSolrServer instance and create a new one is that I have concern
that if it can successfully reconnect to Zookeeper server if Zookeeper
cluster has some issue and reboot. I will do related test with version
Hi Community,
I use Solr(4.10.2) as indexing tool. I use a singleton
CloudSolrServer instance to query Solr. When meet exception, for example
current Solr server not response, i will create a new CloudSolrServer
instance and shutdown the old one. We have many query threads that share the
