Hi,
We are facing the same issues on our setup. 3 zk nodes, 1 shard, 10
collections, 1 replica. v. 5.0.0. default startup params.
Solr Servers: 2 core cpu, 7gb memory
Index size: 28g, 3gb heap
This setup was running on v. 4.6 before upgrading to 5 without any of these
errors. The timeout seems to
Thank you Shawn! Yes - it is now a Solr 5.1.0 cloud on 27 nodes and we
use the startup scripts. The current index size is 3.0T - about 115G
per node - index is stored in HDFS which is spread across those 27 nodes
and about (a guess) - 256 spindles. Each node has 26G of HDFS cache
(MaxDirectM
On 6/3/2015 6:39 PM, Joseph Obernberger wrote:
> Hi All - I've run into a problem where every-once in a while one or more
> of the shards (27 shard cluster) will loose connection to zookeeper and
> report "updates are disabled". In additional to the CLUSTERSTATUS
> timeout errors, which don't seem
Any thoughts on this / anything configuration items I can check? Could
the 180 second clusterstatus timeout messages that I'm getting be
related? Any issue with running 7 nodes in the zookeeper quorum? For
reference the clusterstatus stack trace is:
org.apache.solr.common.SolrException: CLUS
