On the delay in electing a leader when the leader is dead(Solr 7.5)

2020-04-14 Thread Taisuke Miyazaki
Hi, Made Of: tlog replicas + pull replicas Writing: leader and tlog replicas Loading: pull replica only Solr version: 7.5 Number of shards: 1 Write throughput: 1 docs/minutes Number of documents: 4,500,000 Size per document: about 4KB During verification, the replay of the transaction log

facets & docValues

2020-04-14 Thread Revas
We have faceting fields that have been defined as indexed=false, stored=false and docValues=true However we use a lot of subfacets using json facets and facet ranges using facet.queries. We see that after every soft-commit our performance worsens and performs ideal between commits how is that

Re: Fuzzy search not working

2020-04-14 Thread Mike Drob
Pradeep, First, some background on fuzzy term expansions: 1) A query for foobar~2 is really a query for (foobar OR foobar~1 OR foobar~2) 2) Fuzzy term expansion will only take the first 50 terms found in the index and drop the rest. For implementation notes, see this comment -

Learning To Rank with Group Queries

2020-04-14 Thread Webster Homer
Hi, My company is looking at using the Learning to Rank. However, our main searches do grouping. There is an old Jira from 2016 about how these don't work together. https://issues.apache.org/jira/browse/SOLR-8776 It doesn't look like this has moved much since then. When will we be able to

Giant ConcurrentMarkSweep GC activity causing issues in Solr 7

2020-04-14 Thread Anthony Groves
Hi everyone, Hoping to get your thoughts on a nasty GC issue we’ve been having after upgrading our cluster to Solr 7. Our cluster is NOT Solr Cloud, but rather one master node (handles all indexing) and four slave nodes replicating from master (handles all search queries, round robin load

Giant ConcurrentMarkSweep GC activity causing issues in Solr 7

2020-04-14 Thread Anthony Groves
Hi everyone, Hoping to get your thoughts on a nasty GC issue we’ve been having after upgrading our cluster to Solr 7. Our cluster is NOT Solr Cloud, but rather one master node (handles all indexing) and four slave nodes replicating from master (handles all search queries, round robin load