fore making the new searcher live for searchers. I
> would also pause indexing if possible and run queries only to see how it
> runs without indexing.
>
> 3) Try running a query directly to /export handler on each node. Possibly
> one of your nodes is slow for some reason and that is
ly 541 tuples sounds like it might be caused by the caches being
> rebuilt.
>
> In general though the /export handler will slow down as you add more fields
> to the field list and sort list. But if you post your query and information
> on what types the fields are in the field list
We've recently upgraded our SolrCloud (16 shards, 2 replicas) to 6.6.1 on
our way to 7 and I'm getting surprising /stream results.
In one example I /select (wt=csv) and /stream [using
search(...,wt=javabin)] with a query that gives a resultset size of 541
tuples. The select comes back in under a
Hi all,
We're using Solr 4.1.0 and a 15 node Solr Cloud (configured for a 2 minute
autoCommit with no searcher being built). We have a large dataset in
Cassandra and use a Hadoop cluster to read over the dataset, build
documents, and insert them (via CloudSolrServer). That part works as
expected
