On 10/13/2014 11:43 AM, nabil Kouici wrote:
> Thank you for this replay. I don't understand why solr load my shard in
> physical memory before becoming available. Is it related to LRU cache
> management?
Just like with the optimize, this also sounds like something that Solr
would never do. If y
Thank you for this replay. I don't understand why solr load my shard in
physical memory before becoming available. Is it related to LRU cache
management?
Regards,Nabil.
Le Lundi 13 octobre 2014 16h20, Shawn Heisey a écrit
:
On 10/13/2014 1:15 AM, nabil Kouici wrote:
> This gives me
On 10/13/2014 1:15 AM, nabil Kouici wrote:
> This gives me a good understanding. However, I think that slowness in
> start-up in my case is due to segmentation. Before restarting my index
> contains 42 segments with 30GB. After restarting, index is in one segment
> with 22GB. So, I think that sh
Hi Shawn,
This gives me a good understanding. However, I think that slowness in start-up
in my case is due to segmentation. Before restarting my index contains 42
segments with 30GB. After restarting, index is in one segment with 22GB. So, I
think that shard unavailability is coming from optimi
On 10/12/2014 12:46 PM, nabil Kouici wrote:
> I'm evaluating solr performance. I've created implicit collection with 2
> shards in different server. first shard contains 100 million documents
> (30GB), second contain one million document.When I restart the second solr
> instance, shard become im
Hi All,
I'm evaluating solr performance. I've created implicit collection with 2 shards
in different server. first shard contains 100 million documents (30GB), second
contain one million document.When I restart the second solr instance, shard
become immediately available. However, when I restart
