Re: Solr 4.10.3 cached grouping results but Solr 5.2.1 don't, why?

We use grouping, so will try collapsing. Thank you for ideas! -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-4-10-3-cached-grouping-results-but-Solr-5-2-1-don-t-why-tp4224396p4224857.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: GC parameters tuning for core of 140M docs on 50G of heap memory

Very interesting, never heard about that. We tested on our x64 linux with java 1.8.0_51 and result is: java -jar -Xms31g -Xmx31g -Xmn50m memory.jar Total Memory (in bytes): 33279705088 Free Memory (in bytes): 33277314136 Max Memory (in bytes): 33279705088 Elements created and added to LinkedList:

Re: GC parameters tuning for core of 140M docs on 50G of heap memory

On sorting fields we have: -- View this message in context: http://lucene.472066.n3.nabble.com/GC-parameters-tuning-for-core-of-140M-docs-on-50G-of-heap-memory-tp4224813p4224820.html Sent from the Solr - User mailing list archive at Nabble.com.

GC parameters tuning for core of 140M docs on 50G of heap memory

Hi, we have a Solr 5.2.1 with 9 cores and one of them has 140M docs. Can you please recommend tuning of those GC parameters? The performance is not a issue, sometimes during peaks we have OOM and we use 50G of heap memory, the server has 64G of ram. GC_TUNE="-XX:NewRatio=3 \ -XX:SurvivorRatio=4 \

Re: Solr 4.10.3 cached grouping results but Solr 5.2.1 don't, why?

Nobody knows or has the same issue? -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-4-10-3-cached-grouping-results-but-Solr-5-2-1-don-t-why-tp4224396p4224812.html Sent from the Solr - User mailing list archive at Nabble.com.

Solr 4.10.3 cached grouping results but Solr 5.2.1 don't, why?

Hi, we have changed Solr from 4.10.3 to 5.2.1 and we don't know why, but 4.10.3 was caching grouping results and the new 5.2.1 don't. Any suggestion howto cache results? We have 140M docs and some results takes up to 60 secs, so cache will be good. :) I red that grouping using faceting is faster

codec mismatch

Hi, I would like to upgrade from Solr 4.10.3 to Solr 5.2.1 and I have 6 cores all the same version 4.10.3. When I start 5.2.1, 5 cores are started correctly and 1 core (most important 130M docs) fails. I got the message: Error opening new searcher, because: org.apache.lucene.index.CorruptIndexExc

Re: Bad contentType for search handler :text/xml; charset=UTF-8

Hi, our developers solved the problem. We are using Solarium and we had to learn Solarium to use selects with content-type: application/x-www-form-urlencoded Pavel -- View this message in context: http://lucene.472066.n3.nabble.com/Bad-contentType-for-search-handler-text-xml-charset-UTF-8-tp4

Bad contentType for search handler :text/xml; charset=UTF-8

Hi, we have migrated Solr from 5.0 do 5.1 and we can't search now, we have a ERROR for SolrCore like in subject. I can't get any info through Google. Please, can someone help what is going on? Thanks, Pavel -- View this message in context: http://lucene.472066.n3.nabble.com/Bad-contentType-

Re: Optimize SolrCloud without downtime

When we indexing I see the deleted docs are a bit changing.. I was surprised when developer reindex 120M index, we had around 110M of deleted docs and this number was not falling. As you wrote, the typical behavior should be merging deleted docs to 10-20% of whole index? So it should be after two w

Re: Optimize SolrCloud without downtime

Hi, thanks for reply. We have a lot of deleted docs cause we have to reindex all records from time to time, changing some important parameters.. When we do update, it means create and delete. Our deleted docs do not disappear by merging segments. I see our deleted docs are almost the same number