bq: And I also read somewhere that explicit commit is not recommended
in SolrCloud mode
Not quite, it's just easy to have too many commits happen too
frequently from multiple
indexing clients. It's also rare that the benefits of the clients
issuing commits outweighs
the chance of getting it wrong
On 1/4/2016 4:11 PM, Don Bosco Durai wrote:
> Erick, I am using SolrCloud with solrconfig.xml configured with autoCommit.
> And I also read somewhere that explicit commit is not recommended in
> SolrCloud mode. Regarding auto warm, my server has/was been running for a
> while.
Since 4.0, autoCo
Tomás, thanks for the suggestion. facet.mincount will solve my issue.
Erick, I am using SolrCloud with solrconfig.xml configured with autoCommit. And
I also read somewhere that explicit commit is not recommended in SolrCloud
mode. Regarding auto warm, my server has/was been running for a while.
I believe the problem here is that terms from the deleted docs still appear
in the facets, even with a doc count of 0, is that it? Can you use
facet.mincount=1 or would that not be a good fit for your use case?
https://cwiki.apache.org/confluence/display/solr/Faceting#Faceting-Thefacet.mincountPar
Let's be sure we're using terms similarly
That article is from 2010, so is unreliable in the 5.2 world, I'd ignore that.
First, facets should always reflect the latest commit, regardless of
expungeDeletes or optimizes/forcemerges.
_commits_ are definitely recommended. Optimize/forcemerge (or
