should be possible to increase
the number of shards from 2 to 5 or even 8.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-thread-tp4175088p4176046.html
Sent from the Solr - User mailing list archive at Nabble.com.
On 12/23/2014 2:31 AM, heaven wrote:
> We do not use dates here, at least not too often. Usually its something like
> type:Profile (we do use it from the rails application so type describes
> model names), opted_in:true, etc. Solr wasn't running too long though, so
> this could not show the real st
he it shows 1 and 0.84 of the query results. I
also increased the cache size to
autowarm: 512, initial: 1024 and size 4096, which is actually never reached
because of commits.
Best,
Alex
--
View this message in context:
http://lucene.472066.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-t
1190
> cumulative_hits:35938
> cumulative_hitratio:0.7
> cumulative_inserts:15252
> cumulative_evictions:0
>
> Is warmupTime in milliseconds or seconds?
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-thread-tp4175088p4175553.html
> Sent from the Solr - User mailing list archive at Nabble.com.
this message in context:
http://lucene.472066.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-thread-tp4175088p4175553.html
Sent from the Solr - User mailing list archive at Nabble.com.
sn't matter to which node we send requests, SolrCloud decides
> which nodes will process it. Am I wrong?
>
> Best,
> Alex
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-thread-tp4175088p4175285.html
> Sent from the Solr - User mailing list archive at Nabble.com.
sure how to do this now with SolrCloud,
it seems doesn't matter to which node we send requests, SolrCloud decides
which nodes will process it. Am I wrong?
Best,
Alex
--
View this message in context:
http://lucene.472066.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-t
d these options:
> -XX:+UseConcMarkSweepGC
> -XX:+UseLargePages
> -XX:+CMSParallelRemarkEnabled
> -XX:+ParallelRefProcEnabled
> -XX:+UseLargePages
> -XX:+AggressiveOpts
> -XX:CMSInitiatingOccupancyFraction=75
>
> Best,
> Alex
>
>
>
> --
> Vi
Best,
Alex
--
View this message in context:
http://lucene.472066.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-thread-tp4175088p4175271.html
Sent from the Solr - User mailing list archive at Nabble.com.
on formula and all docs have different size but -Xmx is
> already 12G.
>
> Thanks,
> Alex
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-thread-tp4175088p4175227.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
--
Regards,
Shalin Shekhar Mangar.
66.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-thread-tp4175088p4175227.html
Sent from the Solr - User mailing list archive at Nabble.com.
>
>> So I was wondering if that's correct, if this is supposed to be or if
>> something is wrong with our configuration or with Solr.
>>
>> Thanks,
>> Alex
>>
>>
>>
>> --
>> View this message in context:
>> http://lucene.472066.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-thread-tp4175088.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
g is wrong with our configuration or with Solr.
Thanks,
Alex
--
View this message in context:
http://lucene.472066.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-thread-tp4175088.html
Sent from the Solr - User mailing list archive at Nabble.com.
omething is wrong with our configuration or with Solr.
Thanks,
Alex
--
View this message in context:
http://lucene.472066.n3.nabble.com/Endless-100-CPU-usage-on-searcherExecutor-thread-tp4175088.html
Sent from the Solr - User mailing list archive at Nabble.com.
14 matches
Mail list logo