Thanks Erick and Shawn.
I have reduced number of rows per page from 500K to 100K.
I also increased the ZKclientTimeOut to 30 seconds so that I don't run into
ZK time out issues. The ZK cluster has been deployed on the hosts other
than the SolrCloud hosts.
However, I was trying to increase the
Returning 500K rows is, as Shawn says, not Solr's sweet spot.
My guess: All the work you're doing trying to return that many
rows, particularly in SolrCloud mode is simply overloading
your system to the point that the ZK connection times out. Don't
do that. If you need that many rows, either
On 11/18/2016 6:50 PM, Chetas Joshi wrote:
> The numFound is millions but I was also trying with rows= 1 Million. I will
> reduce it to 500K.
>
> I am sorry. It is state.json. I am using Solr 5.5.0
>
> One of the things I am not able to understand is why my ingestion job is
> complaining about
Thanks Erick.
The numFound is millions but I was also trying with rows= 1 Million. I will
reduce it to 500K.
I am sorry. It is state.json. I am using Solr 5.5.0
One of the things I am not able to understand is why my ingestion job is
complaining about "Cannot talk to ZooKeeper - Updates are
The clusterstate on Zookeeper shouldn't be changing
very often, only when nodes come and go.
bq: At that time I am also running queries (that return
millions of docs).
As in rows=milions? This is an anti-pattern, if that's true
then you're probably network saturated and the like. If
you mean
Hi,
I have a SolrCloud (on HDFS) of 50 nodes and a ZK quorum of 5 nodes. The
SolrCloud is having difficulties talking to ZK when I am ingesting data
into the collections. At that time I am also running queries (that return
millions of docs). The ingest job is crying with the the following
