Hi Mark;
I have same situation with my Solr 4.2.1 nodes. These are from my startup
parameters:
-XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75
-XX:NewRatio=3 -XX:MaxTenuringThreshold=8 -XX:+CMSParallelRemarkEnabled
-XX:+ParallelRefProcEnabled -XX:+UseLargePages -XX:+AggressiveOpts
On Apr 18, 2013, at 8:40 AM, jmozah wrote:
>
>
> On 16-Apr-2013, at 11:16 PM, Mark Miller wrote:
>
>> Are you using a the concurrent low pause garbage collector or perhaps G1?
>
>
> I use the default one which comes in jdk 1.7.
It varies by platform, but 99% that means you are using the
On 16-Apr-2013, at 11:16 PM, Mark Miller wrote:
> Are you using a the concurrent low pause garbage collector or perhaps G1?
I use the default one which comes in jdk 1.7.
>
> Are you able to use something like visualvm to pinpoint what the bottleneck
> might be?
Unfortunately.. it is pro
Are you using a the concurrent low pause garbage collector or perhaps G1?
Are you able to use something like visualvm to pinpoint what the bottleneck
might be?
Otherwise, keep raising the timeout. This means Solr and Zk are not able to
talk for that much time - either something needs to be tun
Hi
I am using SolrCloud (4.1) with 6 nodes.
When i index the documents from the mapper and as the load increases.. i see
these messages in my mapper logs…
WHich looks like it is slowing down my indexing speed.
2013-04-16 06:04:18,013 INFO org.apache.solr.common.cloud.ZkStateReader:
Updating li
