Do you seen any (a lot?) of the warming searchers on deck, i.e. value for N:
PERFORMANCE WARNING: Overlapping onDeckSearchers=N
On Wed, May 6, 2015 at 10:58 AM, adfel70 adfe...@gmail.com wrote:
Hello
I have a cluster of 16 shards, 3 replicas. the cluster indexed nested
documents.
it
On Wed, 2015-05-06 at 00:58 -0700, adfel70 wrote:
each shard has around 200 million docs. size of each shard is 250GB.
this runs on 12 machines. each machine has 4 SSD disks and 4 solr processes.
each process has 28GB heap. each machine has 196GB RAM.
[...]
1. heavy GCs when soft commit is
1. yes, I'm sure that pauses are due to GCs. I monitor the cluster and
receive continuously metric from system and from java process.
I see clearly that when soft commit is triggered, major GCs start occurring
(sometimes reocuuring on the same process) and latency rises.
I use CMS GC and jdk
Hello
I have a cluster of 16 shards, 3 replicas. the cluster indexed nested
documents.
it currently has 3 billion documents overall (parent and children).
each shard has around 200 million docs. size of each shard is 250GB.
this runs on 12 machines. each machine has 4 SSD disks and 4 solr
Thank you for the detailed answer.
How can I decrease the impact of opening a searcher in such a large index?
especially the impact of heap usage that causes OOM.
regarding GC tuning - I am doint that.
here are the params I use:
AggresiveOpts
UseLargePages
ParallelRefProcEnabled
I dont see any of these.
I've seen them before in other clusters and uses of SOLR but don't see any
of these messages here.
Dmitry Kan-2 wrote
Do you seen any (a lot?) of the warming searchers on deck, i.e. value for
N:
PERFORMANCE WARNING: Overlapping onDeckSearchers=N
On Wed, May 6,
On 5/6/2015 1:58 AM, adfel70 wrote:
I have a cluster of 16 shards, 3 replicas. the cluster indexed nested
documents.
it currently has 3 billion documents overall (parent and children).
each shard has around 200 million docs. size of each shard is 250GB.
this runs on 12 machines. each machine
On 5/6/2015 8:55 AM, adfel70 wrote:
Thank you for the detailed answer.
How can I decrease the impact of opening a searcher in such a large index?
especially the impact of heap usage that causes OOM.
See the wiki link I sent. It talks about some of the things that
require a lot of heap and
