Re: Requests taking hours on solr cloud

Hi, Are the same requests sometimes stalling and sometimes fast, or is it some particular queries that take hours? There are some things you should avoid with SolrCloud, and deep paging (i.e. a large number for the start or rows parameter) is a typical issue (see e.g. https://yonik.com/solr/

Re: Requests taking hours on solr cloud

Hi Ere, We tried executing this request again and it didn't take any time. So it is not repeatable. average response time of all the queries around this period was only approx 100-200 ms. This was a group=true request where we get 14 groups and 5 results per group. So no deep pagination. On Fri,

Re: Duplicate docs with same unique id on update

Hi, So to be clear - you have a working fix by adding the _root_ field to your schema? I suppose most 8.x users already have a _root_ field, so the thing you are seeing could very well be some bug related to atomic update. Can I propose that you create a minimal reproduction of this issue and

Re: Duplicate docs with same unique id on update

So it was a decision to remove the unique field id and replace it with root? This seems, bad. You can’t have two documents with the same id/unique field. > On Dec 9, 2022, at 7:57 AM, Jan Høydahl wrote: > > Hi, > > So to be clear - you have a working fix by adding the _root_ field to your

Re: Duplicate docs with same unique id on update

No no. The schema still has ONE a uniqueId field. The _root_ field is used as a parent pointer for child documents, it will hold the ID of the parent. Thus you should not need _root_ if you don't use parent/child. But this thread suggests that _root_ may be needed in some other code paths as well

Re: Core reload timeout on Solr 9

tried to enable the -Dsolr.http1=true but it didn’t help. Seeing timeout after 180s (even without sending any traffic to the cluster) and also noticed Caused by: java.util.concurrent.TimeoutException: Total timeout 60 ms elapsed (stacktrace here https://justpaste.it/29bpv

Re: Near Real Time not working as expected

Thank you Tomas! This was really useful info, I checked some of my logs for today... but it say "Registered new searcher autowarm time: 0 ms" I'm very confused right now lol, it sounds odd to have 0ms to me. This is my current Cache connfiguration (I removed the maxWarmingSearchers option as a

Re: Near Real Time not working as expected

Tomas, I just set the max warming searchers to 4, and I still see 0ms on warming time. Not sure what else to check. Thanks in advance! From: Matias Laino Sent: Friday, December 9, 2022 12:10 PM To: Tomás Fernández Löbbe ; users@solr.apache.org Subject: Re: Nea

How to run many SolrClouds within a single K8s cluster?

Hello, We have a single SolrCloud running in K8s (dev env) by implementing a Zookeeper stateful set and a Solr node stateful set. On startup the Solr pods connect to the ZK ensemble defined in the ZK stateful set. If we wanted more SolrClouds in this K8s cluster, would we create more stateful se

Re: Near Real Time not working as expected

> now it's at to 16 and I don't see that ( I went from 6 to 16), but the issue > still persists Just to clarify, the "overlapping ondeck searchers" went away at 16? Assuming that the issue that still persists is docs not being visible? It's tempting to interpret "Registered new searcher autowarm

Using the fq parameter to filter for a value that is multivalued field.

I am having trouble using the fq parameter to filter for a value that is in a muilt-valued field. This works: "myField":["apple"] fq=myField:"apple" document is returned This does not work: "myField":["apple, pear"] fq=myField:"apple" document is NOT returned What do I need to do get fq to

Re: Using the fq parameter to filter for a value that is multivalued field.

"apple, pear" That looks like a string not a multi valued field to me. Maybe I’m wrong but you should have quotes around each element of the array > On Dec 9, 2022, at 12:23 PM, Matthew Castrigno wrote: > > "apple, pear"

Re: Using the fq parameter to filter for a value that is multivalued field.

> On Dec 9, 2022, at 11:22 AM, Matthew Castrigno wrote: > > "myField":["apple, pear"] That's not multivalued. That's a single value and the value is "apple, pear". You need to pass multiple values to Solr for the field when you do your indexing. Basically, you need to pass one myField:ap

Re: Near Real Time not working as expected

Hi Michael! Thanks for helping. > Just to clarify, the "overlapping ondeck searchers" went away at 16? Assuming that the issue that still persists is docs not being visible? Not really, after that I still saw the max overlapping searchers issues up to 6 (even though config was set to 16 which is

Re: Using the fq parameter to filter for a value that is multivalued field.

If you want apple OR pear, use: myField:apple myField:pear If you want apple AND pear, use: +myField:apple +myField:pear wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Dec 9, 2022, at 9:22 AM, Matthew Castrigno wrote: > > I am having trouble usi

Re: How to run many SolrClouds within a single K8s cluster?

On 12/9/22 09:23, mtn search wrote: We have a single SolrCloud running in K8s (dev env) by implementing a Zookeeper stateful set and a Solr node stateful set. On startup the Solr pods connect to the ZK ensemble defined in the ZK stateful set. If we wanted more SolrClouds in this K8s cluster, wo

Re: Using the fq parameter to filter for a value that is multivalued field.

Thank you for your comments that appears to be the root of the problem. Fixing it raises another question. The incorrect multivalued fields were being created with a script line: doc.addField("facets_ss", contentObject.Page.Facets.join(",")); When I try to fix that with: doc.addField("facets_ss"

Re: Using the fq parameter to filter for a value that is multivalued field.

Try adding each value separately. Not joined in code, let solr do the multivalue work, > On Dec 9, 2022, at 1:11 PM, Matthew Castrigno wrote: > >  > Thank you for your comments that appears to be the root of the problem. > > Fixing it raises another question. > > The incorrect multivalued f

Re: Using the fq parameter to filter for a value that is multivalued field.

Thanks Dave. That seems to work. From: Dave Sent: Friday, December 9, 2022 11:19 AM To: Matthew Castrigno Cc: users@solr.apache.org ; a...@petdance.com Subject: Re: Using the fq parameter to filter for a value that is multivalued field. Try adding each value s

Re: Using the fq parameter to filter for a value that is multivalued field.

Of course. Also, remember there are things to consider like if you want to store/retrieve it as an absolute string including capitalization for a facet/Drop down selection or only as a search field. lots of nuances. -Dave

JVM threads and heap issue due to filtercache

Hi, I have a huge sharded collection. Each shard contains 100 millions docs. Queries are using at maximum 20 filter queries. 10 are very often used and the other not often. filterCache size is 10 and autoWarmCount is 10. filterCache statistics are very good except warmupTime is a little long. "C