Adding additional zookeeper on top

Hi Team Can someone let me know if we can do an upgrade to zookeeper ensemble from standalone ?? I have 3 solr nodes with one zookeeper running on one of the node .. and it’s a solr cloud .. so now can I install zookeeper on another node just to make sure it’s not a single point of failure wh

Re: DIH on SolrCloud

Thank you for your quick reply. Can I make sure that the indexing isn't conducted on the node where the DIH executed but conducted on the Leader node, right? As far as I have seen a log, there are errors: the failed establishment of connection occurred from Node2 on the state of Replica on running

Re: DIH on SolrCloud

DIH is deprecated in current Solr versions. The general recommendation is to do processing outside the Solr server and use the update handler (the normal one, not Cell) to add documents to the index. So you should avoid using it as it is not future proof . If you need more Time to migrate to a

DIH on SolrCloud

Hi, All I'm using Solr4.10 with SolrCloud mode. I have 10 Nodes. one of Nodes is Leader Node, the others is Replica.(I will call this Node1 to Node10 for convenience) -> 1 Shard, 1 Leader(Node1), 9 Replica(Node2-10) Indexing always uses DIH of Node2. Therefore, DIH may be executed when Node2 is Le

Re: Force open a searcher in solr.

Please don’t mess with _version_, that’s used internally for optimistic locking. I don’t have a clue, really, whether changing the definition will be deleterious or not. OTOH, that field was presumably defined by people who put the use of _version_ in in the first place, so changing it is just ask

Re: Solr 8.3.1 - NullPointer during Autoscaling

Hmm, not that I know of. This seems like a reasonable JIRA, please raise one. Also, that might get the attention of someone who might have a work-around to offer. Best, Erick > On Aug 13, 2020, at 9:50 AM, Anton Pfennig wrote: > > Hi Erick, > > I found the issue with this NullPointer Issue.

Re: Solr 8.3.1 - NullPointer during Autoscaling

Hi Erick, I found the issue with this NullPointer Issue. If SolrCloud runs on Kubernetes, and if Kubernetes cluster is being scaled, new pods are created with solr nodes on it. The DNS names of the new pods are propagated *AFTER* new solr node instance is created. so the autoscaling work like

Re: Force open a searcher in solr.

So to make things clear, belows what I am expecting I have a document with a unique id field lets say "uniqueID". This document has both stored/indexed and not stored/ not indexed fields Currently I have my pop values in external files but I will instead define a new field in schema (popVal) which

Re: Reaching max Filter cache limit increases the request latencies.

Hey Erick, So I am investigating the point where we can limit the values that are cached using {!cache=false} (we already use it in some of our cases) So in general there is 0 evictions on filter cache side but whenever we hit this max limit there is a spike in evictions as well (which is expected

Re: Solr and commits

Here’s a long explanation: https://lucidworks.com/post/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/ short explanation: 1> yes 2> when the hard commit setting in solrconfig.xml kicks in, regardless the openSearcher setting. Best, Erick > On Aug 13, 2020, at 1:43 AM, Jayadev

Re: Reaching max Filter cache limit increases the request latencies.

Well, when you hit the max capacity, cache entries get aged out and are eligible for GC, so GC activity increases. But for aging out filterCache entries to be noticeable, you have to be flushing a _lot_ of them out. Which, offhand, makes me wonder if you’re using the filterCache appropriately.

Re: Force open a searcher in solr.

Let us know how it works. I want to be sure I’m not confusing you though. There isn’t a “doc ID field”. The structure of an eff file is docid:value where docid is your . What updating numerics does is allow you to update a field in a doc that’s identified by . That field is any name you want as l

Re: Force open a searcher in solr.

Hey Erick, Thanks for the information about the doc ID field. So our external file values are single float value fields and we do use them in functional queries in boost parameter, so based on the definition the above should work. So currently we use solr 5.4.0 but are in the process of upgrading

Re: Incorrect Insecure Settings Check in CoreContainer

Hey Mark, I've fixed it for 8.7 as a part of this ticket here: https://issues.apache.org/jira/browse/SOLR-14748. Thanks for reporting this. Jason On Tue, Aug 11, 2020 at 3:19 PM Jason Gerlowski wrote: > > Yikes, yeah it's hard to argue with that. > > I'm a little confused because I remember tes

Re: Multiple "df" fields

Goodness me, woops, yes, it was a typo -- sorry fo the confusion. We're indeed exploring qf, rather than pf! :). So far it's looking promising! Thanks for your eagle-eye spotting! Best, Edd Edward Turner On Wed, 12 Aug 2020 at 13:15, Erick Erickson wrote: > Probably a typ