happen less often (allowing
it to recover from new documents added and only send the changes with a wider
gap) - but I cant remember what those were.
-Original Message-
From: Andrew Butkus [mailto:andrew.but...@c6-intelligence.com]
Sent: 05 March 2015 14:42
To:
Subject: Re: Solrcloud Index
We had a similar issue, when this happened we did a fetch index on each core
out of sync to put them back right again
Sent from my iPhone
> On 5 Mar 2015, at 14:40, Martin de Vries wrote:
>
> Hi,
>
> We have index corruption on some cores on our Solrcloud running version
> 4.8.1. The index
&shard.info=true
Sent from my iPhone
> On 17 Jan 2015, at 04:23, Naresh Yadav wrote:
>
> Hi all,
>
> We have single solr index with 3 fixed fields(on of field is tokenized with
> space) and rest dynamic fields(string fields in range of 10-20).
>
> Current size of index is 2 GB with around 12
We decided to downgrade to 20 shards again, as we kept having the query time
spikes, if it was a memory issue, I would assume we would have the same
performance issues with 20 shards, so I think this is maybe a problem in solr
rather than our configuration / amount of ram.
In anycase, we have
> Extrapolating what Jack was saying on his reply ... with 100 shards and
> 4 replicas, you have 400 cores that are each about 2.8GB. That results in a
> total index size of just over a terabyte, with 140GB of index data on each of
> the eight servers.
> Assuming you have only one Solr instanc
Hi Shawn,
Thank you for your reply
>The part about memory usage is not clear. That 4GB and 16GB could refer to
>the operating system view of memory, or the view of memory within the JVM.
>I'm curious about how much total >RAM each machine has, how large the Java
>heap is, and what the total
Hi, we have 8 solr servers, split 4x4 across 2 data centers.
We have a collection of around ½ billion documents, split over 100 shards, each
is replicated 4 times on separate nodes (evenly distributed across both data
centers).
The problem we have is that when we use cursormark (and also when w
Hi, we have 8 solr servers, split 4x4 across 2 data centers.
We have a collection of around ½ billion documents, split over 100 shards, each
is replicated 4 times on separate nodes (evenly distributed across both data
centers).
The problem we have is that when we use cursormark (and also wh
