Sent: Tuesday, November 18, 2014 2:45:46 PM GMT -08:00 US/Canada Pacific
Subject: Re: OutOfMemory on 28 docs with facet.method=fc/fcs
On 11/18/2014 3:06 PM, Mohsin Beg Beg wrote:
> Looking at SimpleFacets.java, doesn't fc/fcs iterate only over the DocSet for
> the fields. So assuming eac
Mohsin Beg Beg [mohsin@oracle.com] wrote:
> Looking at SimpleFacets.java, doesn't fc/fcs iterate only over the DocSet for
> the fields.
To get the seed for the concrete faceting resolving, yes. That still leaves the
mapping and the counting structures.
> So assuming each field has a unique
On 11/18/2014 3:06 PM, Mohsin Beg Beg wrote:
> Looking at SimpleFacets.java, doesn't fc/fcs iterate only over the DocSet for
> the fields. So assuming each field has a unique term across the 28 rows, a
> max of 28 * 15 unique small strings (<100bytes), should be in the order of
> 1MB. For 100 co
t...@statsbiblioteket.dk
To: solr-user@lucene.apache.org
Sent: Tuesday, November 18, 2014 12:34:08 PM GMT -08:00 US/Canada Pacific
Subject: RE: OutOfMemory on 28 docs with facet.method=fc/fcs
Mohsin Beg Beg [mohsin@oracle.com] wrote:
> I am getting OOM when faceting on numFound=28.
endent on the number of
hits in the search result.
> If a different solr node is selected that one fails too. Any suggestions ?
> &facet.field=field1field15
> &f.field1...field15.facet.method=fc/fcs
> &collection=Collection1...Collection100
You seem to be issuing a f
/Collection1/query
?q=fieldX:xyz AND fieldY:("r" OR "g" OR "b")
&rows=0
&fq={!cache=false}time:[ TO ]
&facet=true
&facet.sort=count
&facet.missing=false
&facet.mincount=1
&facet.threads=10
&facet.field=field1field15
&f.field1...f
So does it make the most sense then to force, by default,
facet.method=fcs on slave nodes that receive updates every 5 minutes but
with large segments that don't change every update? Right now,
everything I have configured uses facet.method=fc since we don't declare
it at all.
Rando
uot;
On Thu, Dec 5, 2013 at 12:15 AM, Patrick O'Lone wrote:
> Is there any advantage on a Solr slave to receive queries using
> facet.method=fcs instead of the default of facet.method=fc? Most of the
> segment files are unchanged between replication events - but I wasn'
Is there any advantage on a Solr slave to receive queries using
facet.method=fcs instead of the default of facet.method=fc? Most of the
segment files are unchanged between replication events - but I wasn't
sure if replication would cause the unchanged segment field caches to be
lost a
: Is the parameter facet.method=fc still needed ?
https://wiki.apache.org/solr/SimpleFacetParameters#facet.method
"The default value is fc (except for BoolField) since it tends to use less
memory and is faster when a field has many unique terms in the index. "
-Hoss
Is the parameter facet.method=fc still needed ?
Thank you.
Patrick.
11 matches
Mail list logo
