nodes and start them back one after the other.
On 21 May 2015 00:24, "Ryan Steele" wrote:
My SolrCloud cluster isn't reassigning the collections leaders from downed
cores--the downed cores are still listed as the leaders. The cluster has
been in the state for a few hours and the log
I accidentelly used the collections API to add a replica using async and
specified a non-existent node. Is their a way to clear out this job from
the async queue?
Thanks,
Ryan
---
This email has been scanned for
My SolrCloud cluster isn't reassigning the collections leaders from
downed cores--the downed cores are still listed as the leaders. The
cluster has been in the state for a few hours and the logs continue to
report "No registered leader was found after waiting for 4000ms." Is
there a way to forc
What time unit is the Solr collections API overseerstatus action using
in the returned data?
For example, given the following XML: name="avgTimePerRequest">0.15491020578778136
Is the avgTimePerRequest in seconds?
Thanks,
Ryan
---
'll just have to monitor the
cluster as data gets imported into it and make adjustments as needed.
Ryan
On 4/2/15 12:06 AM, Toke Eskildsen wrote:
> Ryan Steele wrote:
>> Does a SolrCloud 5.0 cluster need enough RAM across the cluster to load
>> all the collections into RAM at
Does a SolrCloud 5.0 cluster need enough RAM across the cluster to load
all the collections into RAM at all times?
I'm building a SolrCloud cluster that may have approximately 1 TB of
data spread across the collections.
Thanks,
Ryan
