Re: Too Many Searcher Opening Events

Hi Ronen, If you think that it is unintentional explicit commit that is causing this, you can disable explicit commit with IgnoreCommitOptimizeUpdateProcessorFactory. HTH, Emir -- Monitoring - Log Management - Alerting - Anomaly Detection Solr & Elasticsearch Consulting Support Training - http://

All replicas DOWN after Rebalance leaders | solrcloud v8.7.0

Hello, On solr v8.7.0 we consistently experience shards with all replicas in DOWN state after a node restart and shard rebalanceleaders. During rebalance we stop all /update requests to all shard. Once this issue happens, we see “No Servers Hosting Shard” error in solr log and only remedy is t

Problem with eDisMax and multi-word synonyms

Hi, Here's one that I can't wrap my head around. The main question is: why are the search terms treated differently in eDisMax if the query expands to a multi-word synonym, and there are different field types and q.op=AND? This gets complicated quickly, so I tried to reproduce the results wit

Re: Problem with eDisMax and multi-word synonyms

Hello Ere, The q.op parameter is not a dismax parameter. instead i think you are being bitten bij de mm parameter [1] which by default is 100%, meaning all terms must match. Multi word synonym handing and mm are not a very intuitive match, and can lead to crazy problems. Also beware of mm and stop

Re: question to Collection Aliasing for Time series data

Thinking a little longer, and remembering the code a little more, I suspect removing middle collections probably won't actually error (assuming you actually wanted gaps in your time series and that you don't consider that an error), but any new data that would have hit the removed collection it wou

Re: Too Many Searcher Opening Events

On 2021-04-27 11:07, Ronen Nussbaum wrote: I'm trying to understand why there are so many "SolrIndexSearcher Opening" events in the log e.g. Those events are all for the realtime searcher, which is normally found at the /get handler path. I believe that handler is implicit, meaning you don'

join with big 2nd collection

Hi List, We have a join perfomance issue and are not sure in which direction we should look to solve the issue. We currently only have a single node setup We have 2 collections where we do join querys, joined by a "primary key" string field contentId_s Each dataset for a single contentId_s cons

SecureRandom algorithm 'NativePRNG' is in use

Hi, I intermittently face this issue sometimes while running the unit tests. SecureRandom algorithm 'NativePRNG' is in use by your JVM, which is a potentially blocking algorithm on some environments. Please report the details of this failure (and your JVM vendor/version) to solr-u...@lucene.apach

Re: SecureRandom algorithm 'NativePRNG' is in use

One more thing, -Dtest.solr.allowed.securerandom=NativePRNG doesn't seem to help and I haven't tried the other option yet. On Wed, Apr 28, 2021 at 8:41 PM gnandre wrote: > Hi, > > I intermittently face this issue sometimes while running the unit tests. > > SecureRandom algorithm 'NativePRNG' is

RE: Too Many Searcher Opening Events

Thank you Shawn for your reply. I didn't notice the "realtime", we do use it in our application workflow. I tried to reproduce it in a similar environment but when used the /get handler I only saw this line in the log: "org.apache.solr.handler.component.RealTimeGetComponent LOOKUP_SLICE:shard50=.

Re: Problem with eDisMax and multi-word synonyms

Hello Markus, Thanks for the reply. I'm not sure I understand. The docs state the following: "The default value of mm is 0% (all clauses optional), unless q.op is specified as "AND", in which case mm defaults to 100% (all clauses required)." (https://solr.apache.org/guide/8_8/the-dismax-que