Pagination issue when grouping

Hello, I group search result by a field (with high cardinality) I paginate search page using num of groups using param group.ngroups=true. But that cause high CPU issue. So i turn off it. Without ngroups=true, i can't get the num of groups so pagination is not correct because i must use numFound,

Re: High CPU when use grouping group.ngroups=true

Without using ngroups=true, is there any way to handle pagination correctly when we collapse result using grouping? Regards, Tien On Tue, May 23, 2017 at 9:55 PM, Nguyen Manh Tien wrote: > The collapse field is high-cardinality field. I haven't profiling yet but > will do it.

Re: High CPU when use grouping group.ngroups=true

needs to be done. > > Have you tried profiling to see where the CPU time is being spent? > > Best, > Erick > > On Tue, May 23, 2017 at 7:46 AM, Nguyen Manh Tien > wrote: > > Hi All, > > > > I recently switch from solr field collapse/expand to grouping for > c

High CPU when use grouping group.ngroups=true

Hi All, I recently switch from solr field collapse/expand to grouping for collapse search result All seem good but CPU is always high (80-100%) when i set param group.ngroups=true. We set ngroups=true to get number of groups so that we can paginate search result correctly. Due to CPU issue we nee

Re: Explicit OR in edismax query with mm=100%

dismax respects the mm parameter in your case. > You should set "mm=1", if you want to obtain the results of OR search. > "mm=100%" means that all terms in your query should match. > > Regards, > Yasufumi > > > > On 2017/04/20 10:40, Nguyen Manh Tien

Explicit OR in edismax query with mm=100%

Hi, I run a query "Solr OR Lucene" with defType=edismax and mm=100%. The search result show that query works similar to "Solr AND Lucene" (all terms required) Does edismax ignore mm parameter because i already use OR explicitly here? Thanks, Tien

Re: Increasing number of SolrIndexSearcher (Leakage)?

I found a custom component cause that issue, It creates a SolrQueryRequest but doesn't close at the end that make ref to SolrIndexSearcher don't go to 0 and SIS is not released. > > On Tue, Feb 18, 2014 at 9:31 PM, Yonik Seeley wrote: > On Mon, Feb 17, 2014 at 1:34 A

Re: Solr index filename doesn't match with solr vesion

> > > https://github.com/apache/lucene-solr/blob/lucene_solr_4_6/lucene/core/src/java/org/apache/lucene/codecs/lucene46/Lucene46Codec.java#L50 > > Hope this helps, > Tri > > > On Feb 16, 2014, at 08:52 PM, Shawn Heisey wrote: > > On 2/16/2014 7:25 PM, Nguyen Manh Ti

Increasing number of SolrIndexSearcher (Leakage)?

Hello, My solr got OOM recently after i upgraded from solr 4.0 to 4.6.1. I check heap dump and found that it has many SolrIndexSearcher (SIS) objects (24), i expect only 1 SIS because we have 1 core. I make some experiment - Right after start solr, it has only 1 SolrIndexSearcher - *But after i i

Solr index filename doesn't match with solr vesion

Hello, I upgraded recently from solr 4.0 to solr 4.6, I check solr index folder and found there file _aars_*Lucene41*_0.doc _aars_*Lucene41*_0.pos _aars_*Lucene41*_0.tim _aars_*Lucene41*_0.tip I don't know why it don't have *Lucene46* in file name. Is there something wrong? Thanks, Tien