Re: SolrClient.query take a 'collection' argument

2020-06-05 Thread Shawn Heisey
On 6/5/2020 4:24 PM, Jim Anderson wrote: I am running my first solrj program and it is crashing when I call the method client.query("coreName",queryParms) The API doc says the string should be a collection. I'm still not sure about the difference between a collection and a core, so what I am

SolrClient.query take a 'collection' argument

2020-06-05 Thread Jim Anderson
I am running my first solrj program and it is crashing when I call the method client.query("coreName",queryParms) The API doc says the string should be a collection. I'm still not sure about the difference between a collection and a core, so what I am doing is likely illegal. Given that I have

Getting to grips with auto-scaling

2020-06-05 Thread Tom Evans
Hi I'm trying to get a handle on the newer auto-scaling features in Solr. We're in the process of upgrading an older SolrCloud cluster from 5.5 to 8.5, and re-architecture it slightly to improve performance and automate operations. If I boil it down slightly, currently we have two collections,

Re: Edismax query using different strings for different fields

2020-06-05 Thread Erick Erickson
Let’s see the results of adding =query to the query, in particular the parsed version. Because what you’re reporting doesn’t really make sense. edismax should be totally ignoring the “qf” parameter since you’re specifically qualifying all the clauses with a field. Unless you’re not really

Re: Solr takes time to warm up core with huge data

2020-06-05 Thread Shawn Heisey
On 6/5/2020 12:17 AM, Srinivas Kashyap wrote: q=*:*=PARENT_DOC_ID:100=MODIFY_TS:[1970-01-01T00:00:00Z TO *]=PHY_KEY2:"HQ012206"=PHY_KEY1:"JACK"=1000=MODIFY_TS desc,LOGICAL_SECT_NAME asc,TRACK_ID desc,TRACK_INTER_ID asc,PHY_KEY1 asc,PHY_KEY2 asc,PHY_KEY3 asc,PHY_KEY4 asc,PHY_KEY5 asc,PHY_KEY6

RE: Script to check if solr is running

2020-06-05 Thread Dunigan, Craig A.
A simple cronjob with /bin/solr status and /bin/solr start should do the trick. There must be a Windows equivalent if that’s what you’re using. From: Ryan W Sent: Thursday, June 4, 2020 11:39 AM To: solr-user@lucene.apache.org Subject: Re: Script to check if solr is running WARNING: This

Re: Script to check if solr is running

2020-06-05 Thread Walter Underwood
Most Linux distros are using systemd to manage server processes. https://en.wikipedia.org/wiki/Systemd wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Jun 5, 2020, at 8:08 AM, Mark H. Wood wrote: > > On Thu,

Re: Script to check if solr is running

2020-06-05 Thread Mark H. Wood
On Thu, Jun 04, 2020 at 12:36:30PM -0400, Ryan W wrote: > Does anyone have a script that checks if solr is running and then starts it > if it isn't running? Occasionally my solr stops running even if there has > been no Apache restart. I haven't been able to determine the root cause, > so the

Edismax query using different strings for different fields

2020-06-05 Thread David Zimmermann
I could need some advice on how to handle a particular cross language search with Solr. I posted it on Stackoverflow 2 months ago, but could not find a solution. I have documents in 3 languages (English, German, French). For simplicity let's assume it's just two languages (English and German).

Re: Limit Solr Disk IO

2020-06-05 Thread Erick Erickson
Have you considered TLOG/PULL replicas rather than NRT replicas? That way, all the indexing happens on a single machine and you can use shards.preference to confine the searches happen on the PULL replicas, see: https://lucene.apache.org/solr/guide/7_7/distributed-requests.html No, you can’t

Atomic updates with nested documents

2020-06-05 Thread Ludger Steens
Dear Community, I am using Solr 7.7 and I am wondering how it is possible to do a partial update on nested documents / child documents. Suppose I have committed the following documents to the index: [ { "id": "1", "testString": "1", "testInt": "1", "_childDocuments_": [

Re: Solr takes time to warm up core with huge data

2020-06-05 Thread Erick Erickson
My suspicion, as others have said, is that you simply have too much data on too little hardware. Solr definitely should not be taking this long. Or rather, if Solr is taking this long to start up you have a badly undersized system and until you address that you’ll just be going ‘round in circles.

Re: CDCR behaviour

2020-06-05 Thread Jason Gerlowski
Hi Daniel, Just a heads up that attachments and images are stripped pretty aggressively by the mailing list - none of your images made it through. You might more success linking to the images in Dropbox or some other online storage medium. Best, Jason On Thu, Jun 4, 2020 at 10:55 AM

SolrResourceLoader is not closed when SolrCore is closed

2020-06-05 Thread Michael Aleythe, Sternwald
Hi everybody, I'm currently using solr 8.3.1. While working on tests for a solr plugin I'm writing , I realized that the SolrResourceLoader used by a SolrCore is not closed, when calling SolrCore.close(). This leads to open file handles. Can anybody explain this behavior? Best Regards,

RE: Solr takes time to warm up core with huge data

2020-06-05 Thread Srinivas Kashyap
Hi Jörn, I think, you missed my explanation. We are not using sorting now: The original query: q=*:*=PARENT_DOC_ID:100=MODIFY_TS:[1970-01-01T00:00:00Z TO *]=PHY_KEY2:"HQ012206"=PHY_KEY1:"JACK"=1000=MODIFY_TS desc,LOGICAL_SECT_NAME asc,TRACK_ID desc,TRACK_INTER_ID asc,PHY_KEY1 asc,PHY_KEY2

Re: Solr takes time to warm up core with huge data

2020-06-05 Thread Jörn Franke
I think DIH is the wrong solution for this. If you do an external custom load you will be probably much faster. You have too much JVM memory from my point of view. Reduce it to eight or similar. It seems you are just exporting data so you are better off work the exporting handler. Add

RE: Solr takes time to warm up core with huge data

2020-06-05 Thread Srinivas Kashyap
Thanks Shawn, The filter queries are not complex. Below are the filter queries I’m running for the corresponding schema entry: q=*:*=PARENT_DOC_ID:100=MODIFY_TS:[1970-01-01T00:00:00Z TO *]=PHY_KEY2:"HQ012206"=PHY_KEY1:"JACK"=1000=MODIFY_TS desc,LOGICAL_SECT_NAME asc,TRACK_ID

RE: Autoscaling using SolrCloud8.5 on AWS EKS - issue with Node Added trigger

2020-06-05 Thread Mangla,Kirti
Hi, I am working with solr 8.5.2 on AWS EKS. Autoscaling trigger NodeAddedTrigger is not working and throwing Java error Caused by: org.apache.solr.common.SolrException: org.apache.solr.common.SolrException: Error getting remote info Looking for some help for troubleshooting it. Thanks, Kirti