NPE in QueryComponent.mergeIds when using timeAllowed and sorting SOLR 8.7

Last week I switched to Solr 8.7 from a “special” build of Solr 6.6 The system has a timeout set for querying. I am now seeing this bug. https://issues.apache.org/jira/browse/SOLR-14758 Max Query Time goes from 1.6 seconds to 20 seconds and

NPE in QueryComponent.mergeIds when using timeAllowed and sorting SOLR 8.7

Last week I switched to Solr 8.7 from a “special” build of Solr 6.6 The system has a timeout set for querying. I am now seeing this bug. https://issues.apache.org/jira/browse/SOLR-14758 Max Query Time goes from 1.6 seconds to 20 seconds and

Re: Overriding Sort and boosting some docs to the top

Hello, You are probably looking for the elevator component, check it out: https://lucene.apache.org/solr/guide/8_8/the-query-elevation-component.html Regards, Markus Op wo 24 feb. 2021 om 11:59 schreef Mark Robinson : > Hi, > > I wanted to sort and then boost some docs to the top and these

Re: Handling Locales in Solr

Hello, We put all our customers in the same core/collection because of this, it is not practical to manage hundreds of cores, including their small overhead. Although it can be advantageous when it comes to relevance tuning, no skewed statistics because of other customers. In your case, an

Re: Overriding Sort and boosting some docs to the top

Thanks Marcus for your response. Best, Mark On Wed, Feb 24, 2021 at 4:50 PM Markus Jelsma wrote: > I would stick to the query elevation component, it is pretty fast and > easier to handle/configure elevation IDs, instead of using function queries > for it. We have customers that set a dozen of

Overriding Sort and boosting some docs to the top

Hi, I wanted to sort and then boost some docs to the top and these docs should be my first set in the results and the following ones appearing according to my sort criteria. I understand that sort overrides bq hence bq may not be used in this case - I brought my boost into sort using "query()"

Handling Locales in Solr

Hi everyone, First up thanks for this group, I appreciate it very much for exchanging opinions on how to use Solr. We built a Solr instance for one of our customers which is used for searching data on his website. We need to search different data (kb articles, products and external links) in

Re: Overriding Sort and boosting some docs to the top

I would stick to the query elevation component, it is pretty fast and easier to handle/configure elevation IDs, instead of using function queries for it. We have customers that set a dozen of documents for a given query and it works just fine. I also do not expect the function query variant to be

Re: Overriding Sort and boosting some docs to the top

Thanks for the reply Markus! I did try it. My question specifically was (repasting here):- Which is more recommended/ performant? Note:- Assume that I have hundreds of ids to boost like this. Is there a difference to the answer if docs to be boosted after the sort is less? Thanks! Mark On

RE: Dynamic starting or stoping of zookeepers in a cluster

One doubt about it: In order to have a highly available zookeeper, you must have at least three separate physical servers for ZK. Running multiple zookeepers on one physical machine gains you nothing ... because if the whole machine fails, you lose all of those zookeepers. If you have three

Re: Dynamic starting or stoping of zookeepers in a cluster

On 2/24/2021 9:04 AM, DAVID MARTIN NIETO wrote: If I'm not mistaken the number of zookeepers must be odd. Having 3 zoos on 3 different machines, if we temporarily lost one of the three machines, we would have only two running and it would be an even number.Would it be advisable in this case

Solr 7.6.0 - OOM Caused Down Replica. Cannot recover. Please advice

Hi everyone, We had an OOM event earlier this morning. This has caused one of our shards to lose all it's replicas and it's leader is still in a down state. We have restarted the Java process (solr) and it's still in a down state. Logs below: ``` Feb 25, 2021 @ 11:46:43.000 2021-02-25

What controls field cache size and eviction rates?

Hi SOLR Community, I've been trying to understand how the field cache in SOLR manages its evictions, and it is not easily readable from the code or documentation the simple question of when and how something gets evicted from the field cache. This cache also doesn't show hit ratio, total hits,

Re: Solr Cloud Autoscaling Basics

Any pointers here would be appreciated :) -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html