Re: Solr Cloud Autoscaling Basics

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

Re: Solr Cloud freezes during scheduled backup

Hi Pawel, This definitely sounds like garbage collection biting you. Backups themselves aren't usually memory intensive, but if indexing is going on at the same time you should expect elevated memory usage. Essentially this is because for each core being backed up, Solr needs to hold pieces of tw

Re: Solr cloud facet query returning incorrect results

This should work as you expect, so the first thing I’d do is add &debug=query and see the parsed query in both cases. If that doesn’t show anything, please post the full debug response in both cases. Best, Erick > On Dec 21, 2020, at 4:31 AM, Alok Bhandari wrote: > > Hello All , > > we are

Re: Solr cloud issuse: Async exception during distributed update

Hi, sounds like https://issues.apache.org/jira/browse/SOLR-13963 which was fixed in Solr 8.3.1 On Thu, 10 Dec 2020 at 06:20, Ritvik Sharma wrote: > Hi Houston, > Thanks for reply > > We dont have this kind of field. It's a field value and it is coming > randomly, not all the time. > We are index

Re: Solr cloud issuse: Async exception during distributed update

Hi Houston, Thanks for reply We dont have this kind of field. It's a field value and it is coming randomly, not all the time. We are indexing using cloudsolrclient + spring data . It is coming on any value, I am trying to do indexing of ~30 million records. And it is coming on Solr cloud mode n

Re: Solr cloud issuse: Async exception during distributed update

Do you have a field named "314257s_seourls" in your schema? Is there a dynamic field you are trying to match with that name? - Houston On Thu, Dec 10, 2020 at 2:53 PM ritvik wrote: > Hi , > Please suggest, why it is happening. > > > > -- > Sent from: https://lucene.472066.n3.nabble.com/Solr-U

Re: Solr cloud issuse: Async exception during distributed update

Hi , Please suggest, why it is happening. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Solr cloud issuse: Async exception during distributed update

Hi Furkan I have added the mail. Please check. On Wed, 9 Dec 2020 at 12:52, Furkan KAMACI wrote: > Hi Ritwik, > > Could you send your e-mail to solr user list? > > Kind Regards, > Furkan KAMACI > > On 9 Dec 2020 Wed at 10:18 Ritvik Sharma wrote: > >> >> Hi Solr Owner , >> >> Please check th

Re: Solr Cloud 8.5.1 - HDFS and Erasure Coding

I am not aware of a test. However keep In mind that HDFS supported will be deprecated. Additionally - you can configure erasure encoding in HDFS on a per folder / file basis so you could in the worst case just make the folder for Solr with the standard HDFS mode. Erasure encoding has several li

Re: Solr Cloud Query when one of the Solr instances goes down

Hi Tyrone, We use an external load balancer across the nodes. If you use the java client you can query the zookeepers https://lucene.apache.org/solr/guide/7_1/solrcloud-query-routing-and-read-tolerance.html SolrCloud Query Routing And Read Tolerance | Apache Solr Reference Guide 7.1

Re: Solr cloud backup/restore not working

On 6/17/2020 8:55 PM, yaswanth kumar wrote: Caused by: javax.crypto.BadPaddingException: RSA private key operation failed Something appears to be wrong with the private key that Solr is attempting to use for a certificate. Best guess, incorporating everything I can see in the stacktrace, is

Re: Solr cloud backup/restore not working

On 6/16/2020 8:44 AM, yaswanth kumar wrote: I don't see anything related in the solr.log file for the same error. Not sure if there is anyother place where I can check for this. The underlying request that failed might be happening on one of the other nodes in the cloud. It might be necessary

Re: Solr cloud backup/restore not working

nesday, June 17, 2020 4:33 PM > To: solr-user@lucene.apache.org > Subject: Re: Solr cloud backup/restore not working > > ATTENTION: External Email – Be Suspicious of Attachments, Links and > Requests for Login Information. > > Can someone please guide me on where can I get mor

RE: Solr cloud backup/restore not working

user@lucene.apache.org Subject: Re: Solr cloud backup/restore not working ATTENTION: External Email – Be Suspicious of Attachments, Links and Requests for Login Information. Can someone please guide me on where can I get more detailed error of the above exception while doing restore?? All that I se

Re: Solr cloud backup/restore not working

Can someone please guide me on where can I get more detailed error of the above exception while doing restore?? All that I see in solr.log was pasted above Thanks, On Tue, Jun 16, 2020 at 10:44 AM yaswanth kumar wrote: > I don't see anything related in the solr.log file for the same error. Not

Re: Solr cloud backup/restore not working

I don't see anything related in the solr.log file for the same error. Not sure if there is anyother place where I can check for this. Thanks, On Tue, Jun 16, 2020 at 10:21 AM Shawn Heisey wrote: > On 6/12/2020 8:38 AM, yaswanth kumar wrote: > > Using solr 8.2.0 and setup a cloud with 2 nodes. (

Re: Solr cloud backup/restore not working

On 6/12/2020 8:38 AM, yaswanth kumar wrote: Using solr 8.2.0 and setup a cloud with 2 nodes. (2 replica's for each collection) Enabled basic authentication and gave all access to the admin user Now trying to use solr cloud backup/restore API, backup is working great, but when trying to invoke re

Re: Solr cloud backup/restore not working

Sure I pasted it below from the solr logfiles.. 2020-06-16 14:06:27.000 INFO (qtp1987693491-153) [c:test ] o.a.s.s.HttpSolrCall [admin] webapp=null path=/admin/collections params={name=test&action=RESTORE&location=/opt/$ 2020-06-16 14:06:27.001 ERROR (qtp1987693491-153) [c:test ] o.a.s.s.Http

Re: Solr cloud backup/restore not working

Have you looked in the Solr logfiles? > Am 16.06.2020 um 05:46 schrieb yaswanth kumar : > > Can anyone here help on the posted question pls?? > >> On Fri, Jun 12, 2020 at 10:38 AM yaswanth kumar >> wrote: >> >> Using solr 8.2.0 and setup a cloud with 2 nodes. (2 replica's for each >> collecti

Re: Solr cloud backup/restore not working

Can anyone here help on the posted question pls?? On Fri, Jun 12, 2020 at 10:38 AM yaswanth kumar wrote: > Using solr 8.2.0 and setup a cloud with 2 nodes. (2 replica's for each > collection) > Enabled basic authentication and gave all access to the admin user > > Now trying to use solr cloud ba

Re: SOLR Cloud: 1500+ threads are in TIMED_WAITING status

Hi, Is there any solution found for this issue. We are using Solr 7.6 and sometimes we do see lot of QTP threads with the stack trace sun.misc.Unsafe.park(Native method) java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) java.util.concurrent.locks.AbstractQueuedSynchronizer$Co

Re: Solr Cloud on Docker?

er@lucene.apache.org > <mailto:solr-user@lucene.apache.org> <mailto:solr-user@lucene.apache.org>> > Subject: Re: Solr Cloud on Docker? > > Thank you Dwane. Great info :) > > > Le mer. 5 févr. 2020 à 11:49, Dwane Hall a écrit : > >> Hey Dominique, &

Re: Solr cloud production set up

Hi Rajdeep, 1. I assume you had enabled docValues for the facet fields, right? 2. What does your GC logs tell? Do you get freezes and CPU spikes during intervals? 3. Caching will help in querying. I'll need to see a sample query of yours to recommend what you can tweak. On Tue, 2

Re: Solr Cloud Question

Assuming that the Solr node you stop does not contain all of the replicas for any shard, there should really be no effect. I do strongly recommend that you stop the node gracefully if possible unless what you really want to test is when a node goes away mysteriously... What’ll happen is that al

Re: Solr Cloud on Docker?

of the new shard creation. Very happy. From: Dominique Bejean Sent: 05 February 2020 17:53 To: Dwane Hall Cc: Scott Stults ; solr-user@lucene.apache.org Subject: Re: Solr Cloud on Docker? Thank you Dwane. Great info :) Le mer. 5 févr. 2020 à 11:49, Dwane Hal

Re: Solr Cloud on Docker?

for your own conditions and best of luck > with your deployment! > > Dwane > > ------ > *From:* Scott Stults > *Sent:* Thursday, 30 January 2020 1:45 AM > *To:* solr-user@lucene.apache.org > *Subject:* Re: Solr Cloud on Docker? > > One

Re: Solr Cloud on Docker?

when capacity planning and recommend reading it (https://sbdevel.wordpress.com/2016/11/30/70tb-16b-docs-4-machines-1-solrcloud/). As always it's recommend to test for your own conditions and best of luck with your deployment! Dwane From: Scott Stults Sen

Re: Solr Cloud on Docker?

One of our clients has been running a big Solr Cloud (100-ish nodes, TB index, billions of docs) in kubernetes for over a year and it's been wonderful. I think during that time the biggest scrapes we got were when we ran out of disk space. Performance and reliability has been solid otherwise. Like

Re: Solr cloud production set up

Hi Rajdeep, Unfortunately it's near impossible for anyone here to tell you what parameters to tweak. People might take guesses based on their individual past experience, but ultimately those are just guesses. There are just too many variables affecting Solr performance for anyone to have a good

Re: Solr Cloud on Docker?

Hi Dwane, Thank you for sharing this great solr/docker user story. According to your Solr/JVM memory requirements (Heap size + MetaSpace + OffHeap size) are you specifying specific settings in docker-compose files (mem_limit, mem_reservation, mem_swappiness, ...) ? I suppose you are limiting tot

Re: Solr cloud production set up

Please suggest anyone On Sun, 19 Jan, 2020, 9:43 AM Rajdeep Sahoo, wrote: > Apart from reducing no of facets in the query, is there any other query > params or gc params or heap space or anything else that we need to tweak > for improving search response time. > > On Sun, 19 Jan, 2020, 3:15 AM E

Re: Solr cloud production set up

Apart from reducing no of facets in the query, is there any other query params or gc params or heap space or anything else that we need to tweak for improving search response time. On Sun, 19 Jan, 2020, 3:15 AM Erick Erickson, wrote: > Add &debug=timing to the query and it’ll show you the time e

Re: Solr cloud production set up

Add &debug=timing to the query and it’ll show you the time each component takes. > On Jan 18, 2020, at 1:50 PM, Rajdeep Sahoo wrote: > > Thanks for the suggestion, > > Is there any way to get the info which operation or which query params are > increasing the response time. > > > On Sat, 18 J

Re: Solr cloud production set up

Thanks for the suggestion, Is there any way to get the info which operation or which query params are increasing the response time. On Sat, 18 Jan, 2020, 11:59 PM Dave, wrote: > If you’re not getting values, don’t ask for the facet. Facets are > expensive as hell, maybe you should think more

Re: Solr cloud production set up

If you’re not getting values, don’t ask for the facet. Facets are expensive as hell, maybe you should think more about your query’s than your infrastructure, solr cloud won’t help you at all especially if your asking for things you don’t need > On Jan 18, 2020, at 1:25 PM, Rajdeep Sahoo wrote:

Re: Solr cloud production set up

We have assigned 16 gb out of 24gb for heap . No other process is running on that node. 200 facets fields are there in the query but we will not be getting the values for each facets for every search. There can be max of 50-60 facets for which we will be getting values. We are using caching,is

Re: Solr cloud production set up

On 1/18/2020 10:09 AM, Rajdeep Sahoo wrote: We are having 2.3 million documents and size is 2.5 gb. 10 core cpu and 24 gb ram . 16 slave nodes. Still some of the queries are taking 50 sec at solr end. As we are using solr 4.6 . Other thing is we are having 200 (avg) facet fields in a q

Re: Solr cloud production set up

Although we are having a avg of 200 facet fields in the search request all of them will not be having values in each request. Max of 50-60 facet fields will be having some value. And we are using function query,is it having some performance impact. On Sat, 18 Jan, 2020, 11:10 PM Walter Unde

Re: Solr cloud production set up

For indexing, is the master node CPU around 90%? If not, you aren’t sending requests fast enough or your disk is slow. For querying, 200 facet fields is HUGE. That will take a lot of Java heap memory and will be slow. Each facet fields requires large in-memory arrays and sorting. wunder Walter

Re: Solr cloud production set up

Hi shawn, Thanks for this info, Could you Please address my below query, We are having 2.3 million documents and size is 2.5 gb. With this data do we need solr cloud. 10 core cpu and 24 gb ram . 16 slave nodes. Still some of the queries are taking 50 sec at solr end. As we are using solr

Re: Solr cloud production set up

On 1/18/2020 9:55 AM, Rajdeep Sahoo wrote: We do parallel indexing in production, What about search performance in solr cloud in comparison with master slave. And what about block join performance in solr cloud. Do we need to increase the infra for solr cloud as we would be maintainin

Re: Solr cloud production set up

We are having 2.3 million documents and size is 2.5 gb. 10 core cpu and 24 gb ram . 16 slave nodes. Still some of the queries are taking 50 sec at solr end. As we are using solr 4.6 . Other thing is we are having 200 (avg) facet fields in a query. And 30 searchable fields. Is there any wa

Re: Solr cloud production set up

Agreed with the above. what’s your idea of “huge”? I have 600 ish gb in one core plus another 250x2 in two more on the same standalone solr instance and it runs more than fine > On Jan 18, 2020, at 11:31 AM, Shawn Heisey wrote: > > On 1/18/2020 1:05 AM, Rajdeep Sahoo wrote: >> Our Index size

Re: Solr cloud production set up

Hi shawn, Thanks for your reply We do parallel indexing in production, What about search performance in solr cloud in comparison with master slave. And what about block join performance in solr cloud. Do we need to increase the infra for solr cloud as we would be maintaining multiple sha

Re: Solr cloud production set up

On 1/18/2020 1:05 AM, Rajdeep Sahoo wrote: Our Index size is huge and in master slave the full indexing time is almost 24 hrs. In future the no of documents will increase. So,please some one recommend about the no of nodes and configuration like ram and cpu core for solr cloud. Indexing is

Re: Solr cloud production set up

Got your point. If we think about the infra, then in cloud do we need more infra in comparison to master slave. On Sat, 18 Jan, 2020, 2:24 PM Jörn Franke, wrote: > I think you should do your own measurements. This is very document and > processing specific. > You can run a test with a simple

Re: Solr cloud production set up

I think you should do your own measurements. This is very document and processing specific. You can run a test with a simple setup for let’s say 1 mio document and interpolate from this. It could be also that your ETL is the bottleneck and not Solr. At the same time you can simulate user queries

Re: Solr cloud production set up

How big? We index 35 million documents in about 6 hours. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Jan 18, 2020, at 12:05 AM, Rajdeep Sahoo > wrote: > > Our Index size is huge and in master slave the full indexing time is almost > 24 hrs. >

Re: Solr cloud production set up

Our Index size is huge and in master slave the full indexing time is almost 24 hrs. In future the no of documents will increase. So,please some one recommend about the no of nodes and configuration like ram and cpu core for solr cloud. On Sat, 18 Jan, 2020, 8:05 AM Walter Underwood, wrote: >

Re: Solr cloud production set up

Why do you want to change to Solr Cloud? Master/slave is a great, stable cluster architecture. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Jan 17, 2020, at 6:19 PM, Rajdeep Sahoo wrote: > > Please reply anyone > > On Sat, 18 Jan, 2020, 12:13 A

Re: Solr cloud production set up

Please reply anyone On Sat, 18 Jan, 2020, 12:13 AM Rajdeep Sahoo, wrote: > Hi all, > We are using solr cloud 7.7.1 > In a live production environment how many solr cloud server do we need, > Currently ,we are using master slave set up with 16 slave server with > solr 4.6. > In solr cloud do we

Re: Solr Cloud on Docker?

Hey Walter, I recently migrated our Solr cluster to Docker and am very pleased I did so. We run relativity large servers and run multiple Solr instances per physical host and having managed Solr upgrades on bare metal installs since Solr 5, containerisation has been a blessing (currently Solr 7

Re: Solr-Cloud, join and collection collocation

> Note: adding score=none as a local param. Turns another algorithm > dragging by from side join. Indeed, the behavior with score=none local param is a query time correlated with the joined collection subset size. For subset of 100k documenrs, the query time is 1 seconds, 4 sec for 1M I get client

Re: Solr-Cloud, join and collection collocation

Note: adding score=none as a local param. Turns another algorithm dragging by from side join. On Wed, Oct 16, 2019 at 11:37 AM Nicolas Paris wrote: > Sadly, the join performances are poor. > The joined collection is 12M documents, and the performances are 6k ms > versus 60ms when I compare to th

Re: Solr-Cloud, join and collection collocation

Sadly, the join performances are poor. The joined collection is 12M documents, and the performances are 6k ms versus 60ms when I compare to the denormalized field. Apparently, the performances does not change when the filter on the joined collection is changed. It is still 6k ms when the subset is

Re: Solr-Cloud, join and collection collocation

> You can certainly replicate the joined collection to every shard. It > must fit in one shard and a replica of that shard must be co-located > with every replica of the “to” collection. Yes, I found this in the documentation, with a clear example just after this mail. I will test it today. I also

Re: Solr-Cloud, join and collection collocation

You can certainly replicate the joined collection to every shard. It must fit in one shard and a replica of that shard must be co-located with every replica of the “to” collection. Have you looked at streaming and “streaming expressions"? It does not have the same problem, although it does have

Re: SOLR Cloud: Few cores goes to recovery mode all of a sudden

Thanks Erick, ulimit in all three lodes are more than 65K including max process list. If you look at the timestamp the core down error happened ahead of unable to create thread error, and also core down error took place in node1 and unable to create thread error took place in node3. BTW we are r

Re: SOLR Cloud: Few cores goes to recovery mode all of a sudden

The “unable to create new thread” is where I’d focus first. It means you’re running out of some system resources and it’s quite possible that your other problems are arising from that root cause. What are you “ulimit” settings? the number of file handles and processes should be set to 65k at le

Re: Solr cloud questions

On 8/15/2019 8:14 AM, Kojo wrote: I am starting to think that my setup has more than one problem. As I said before, I am not balancing my load to Solr nodes, and I have eight nodes. All of my web application requests go to one Solr node, the only one that dies. If I distribute the load across the

Re: Solr cloud questions

Ere, thanks for the advice. I don´t have this specific use case, but I am doing some operations that I think could be risky, due to the first time I am using. There is a page that groups by one specific attribute of documents distributed accros shards. I am using Composite ID to allow grouping cor

Re: Solr cloud questions

Does your web application, by any chance, allow deep paging or something like that which requires returning rows at the end of a large result set? Something like a query where you could have parameters like &rows=10&start=100 ? That can easily cause OOM with Solr when using a sharded index. It

Re: Solr cloud questions

Erick, I am using Python, so I think SolrJ is not an option. I wrote my libs to connect to Solr and interpret Solr data. I will try to load balance via Apache that is in front of Solr, before I change my setup, I think it will be simpler. I was not aware about the single point of failure on Solr C

Re: Solr cloud questions

OK, if you’re sending HTTP requests to a single node, that’s something of an anti-pattern unless it’s a load balancer that sends request to random nodes in the cluster. Do note that even if you do send all http requests to one node, the top-level request will be forwarded to other nodes in the clus

Re: Solr cloud questions

Erick, I am starting to think that my setup has more than one problem. As I said before, I am not balancing my load to Solr nodes, and I have eight nodes. All of my web application requests go to one Solr node, the only one that dies. If I distribute the load across the other nodes, is it possible

Re: Solr cloud questions

Kojo: On the surface, this is a reasonable configuration. Note that you may still want to decrease the Java heap, but only if you have enough “head room” for memory spikes. How do you know if you have “head room”? Unfortunately the only good answer is “you have to test”. You can look at the GC

Re: Solr cloud questions

Shawn, Only my web application access this solr. at a first look at http server logs I didnt find something different. Sometimes I have a very big crawler access to my servers, this was my first bet. No scheduled crons running at this time too. I think that I will reconfigure my boxes with two

Re: Solr cloud questions

On 8/13/2019 9:28 AM, Kojo wrote: Here are the last two gc logs: https://send.firefox.com/download/6cc902670aa6f7dd/#Ee568G9vUtyK5zr-nAJoMQ Thank you for that. Analyzing the 20MB gc log actually looks like a pretty healthy system. That log covers 58 hours of runtime, and everything looks ver

Re: Solr cloud questions

Shawn, Here are the last two gc logs: https://send.firefox.com/download/6cc902670aa6f7dd/#Ee568G9vUtyK5zr-nAJoMQ Thank you, Koji Em ter, 13 de ago de 2019 às 09:33, Shawn Heisey escreveu: > On 8/13/2019 6:19 AM, Kojo wrote: > > -- > > tail -f node1/logs/solr_oom_killer-8983-2019

Re: Solr cloud questions

On 8/13/2019 6:19 AM, Kojo wrote: -- tail -f node1/logs/solr_oom_killer-8983-2019-08-11_22_57_56.log Running OOM killer script for process 38788 for Solr on port 8983 Killed process 38788 -- Based on what I can see, a 6GB heap is not big enough for the setup you've got

Re: Solr cloud questions

Erick and Shawn, thank you very much for the very usefull information. When I start to move from sigle Solr to cloud, I was planning to use the cluster for very large collections. But the collection that I said, will not grow that much, so I will downsize shards. Thanks for the information abou

Re: Solr cloud questions

On 8/12/2019 5:47 AM, Kojo wrote: I am using Solr cloud on this configuration: 2 boxes (one Solr in each box) 4 instances per box Why are you running multiple instances on one server? For most setups, this has too much overhead. A single instance can handle many indexes. The only good reas

Re: Solr cloud questions

Kojo: The solr logs should give you a much better idea of what the triggering event was. Just increasing the heap doesn’t guarantee much, again the Solr logs will report the OOM exception if it’s memory-related. You haven’t told us what your physical RAM is nor how much you’re allocating to he

Re: Solr Cloud Kerberos cookie rejected spnego

Hi Team, Enabled solrcloud-7.4.0 with kerberos. While creating a collection getting below error org.apache.http.impl.auth.HttpAuthenticator; NEGOTIATE authentication error: No valid credentials provided (Mechanism level: No valid credentials provided (Mechanism level: Server not found in Kerberos

Re: Solr Cloud Kerberos cookie rejected spnego

I don't think a Kerberos ticket without the hostname makes sense. You almost always need a valid hostname and DNS for Kerberos to work successfully. Kevin Risden On Sun, Jun 23, 2019 at 10:54 AM Rakesh Enjala wrote: > Hi Team, > > Enabled solrcloud-7.4.0 with kerberos. While creating a collect

Re: Solr cloud setup

First of all, do not shard unless necessary to handle your QPS requirements. Sharding adds overhead and has some functionality limitations. How to define “necessary”? Load test a single shard (or even stand-alone with a single core) until it falls over. See: https://lucidworks.com/2012/07/23/si

Re: Solr cloud setup

Hi Abhishek, Here is a nice blog post about migrating to SolrCloud: https://sematext.com/blog/solr-master-slave-solrcloud-migration/ Re number of shards - there is no definite answer - it depends on your indexing/search latency

RE: Solr Cloud configuration

- From: Shawn Heisey Sent: Friday, April 26, 2019 9:45 AM To: solr-user@lucene.apache.org Subject: Re: Solr Cloud configuration On 4/26/2019 6:14 AM, Sadiki Latty wrote: > What you're saying makes sense but is it achievable without downtime? i.e: Is > it achievable to change the

Re: Solr Cloud configuration

On 4/26/2019 6:14 AM, Sadiki Latty wrote: What you're saying makes sense but is it achievable without downtime? i.e: Is it achievable to change the replication factor to 2 as you suggest, and Solr puts the sharded documents back together then replicate? Just changing the replicationFactor par

Re: Solr Cloud configuration

-Original Message- From: Jörn Franke Sent: Thursday, April 25, 2019 5:15 PM To: solr-user@lucene.apache.org Subject: Re: Solr Cloud configuration Are the replicas on the other node? Am 25.04.2019 um 22:44 schrieb Sadiki Latty : Hi, I am doing some testing with Solr Cloud and I have a c

RE: Solr Cloud configuration

Sent: Thursday, April 25, 2019 7:44 PM To: solr-user@lucene.apache.org Subject: Re: Solr Cloud configuration On 4/25/2019 2:44 PM, Sadiki Latty wrote: > - replica 1 > > If I need to upgrade Solr, the recommended method is to update one at a time. > However, when I bring down on

RE: Solr Cloud configuration

I don't have any replicas the 2 Solr instances are both leaders and are split between the two. -Original Message- From: Jörn Franke Sent: Thursday, April 25, 2019 5:15 PM To: solr-user@lucene.apache.org Subject: Re: Solr Cloud configuration Are the replicas on the other node?

Re: Solr Cloud configuration

On 4/25/2019 2:44 PM, Sadiki Latty wrote: - replica 1 If I need to upgrade Solr, the recommended method is to update one at a time. However, when I bring down one Solr instance I noticed that queries no longer work and I get the error "no servers hosting shard" from the node that is u

Re: Solr Cloud configuration

Are the replicas on the other node? > Am 25.04.2019 um 22:44 schrieb Sadiki Latty : > > Hi, > > I am doing some testing with Solr Cloud and I have a couple questions. > Consider this config: > > - 2 Solr instances > > - 3 ZK instances (2 of which are co-located on the same se

RE: solr cloud version upgrade 7.6 to 7.7 collection indexes all marked as down

ot related, is this a known thing? Or shall i open an issue. Thanks, Markus -Original message- > From:Jeff Courtade > Sent: Friday 15th February 2019 21:54 > To: solr-user@lucene.apache.org > Subject: Re: solr cloud version upgrade 7.6 to 7.7 collection indexes all >

Re: solr cloud version upgrade 7.6 to 7.7 collection indexes all marked as down

Yes... nothing in the logs does mean that there was nothing of interest. I have actual entries. This is a test environment so this isn't an emergency. Thanks for the clarification about what I should be seeing. I was just so flabbergasted by this because it's so strange I had to tell somebody and

Re: solr cloud version upgrade 7.6 to 7.7 collection indexes all marked as down

Hmmm. I'm assuming that "nothing in the logs" is node/logs/solr.log, and that you're not finding errors/exceptipons. Just sanity checking here. My guess: you're picking up the default SOLR_HOME which is in your new installation directory and all your replicas are under the old install directory.

Re: solr cloud version upgrade 7.6 to 7.7 collection indexes all marked as down

Hi, Which version of zookeeper are you using? Also, if you tried to query the index, did you get any error message? Regards, Edwin On Fri, 15 Feb 2019 at 02:34, Jeff Courtade wrote: > Hi, > > I am working n doing a simple point upgrade from solr 7.6 to 7.7 cloud. > > 6 servers > 3 zookeepers

Re: Solr Cloud existing shards down after enabling SSL

When you generate the keystore, did you include the IP address of both servers? Regards, Edwin On Mon, 11 Feb 2019 at 21:06, Rakesh Enjala wrote: > Please help > *Regards,* > *Rakesh Enjala* > > > On Wed, Feb 6, 2019 at 2:59 PM Rakesh Enjala > wrote: > > > Hi, > > > > We have a solr cloud with

Re: Solr Cloud existing shards down after enabling SSL

Please help *Regards,* *Rakesh Enjala* On Wed, Feb 6, 2019 at 2:59 PM Rakesh Enjala wrote: > Hi, > > We have a solr cloud with 4 nodes installed in two different servers( 1 > on on server and 3 on other server)and a collection with data in 4 shards. > We have enabled SSL for solrcloud by usin

Re: Solr Cloud Issue

I think the -c option should be unnecessary if -z is supplied. And it works on the other machines. Take a look at the solr.log files on the nodes that doesn't start, that might give more information. Or start with the -f option, that'll log to the foreground and you'll probably see a better messag

Re: Solr Cloud Issue

AFAIK, to start as SolrCloud you should add "-c" switch option as below: bin/solr start -c -z 192.168.1.6:2181,192.168.1.7:2181, 192.168.1.102:2181/solr Otherwise, you'll be starting as standalone Solr instance. Edward On Mon, Jan 21, 2019 at 3:15 PM wrote: > Hello, > > I am configuring the

Re: Solr Cloud wiping all cores when restart without proper zookeeper directories

Chris, These are the steps to reproduce the issue not actually deleting it. Solr is deleting data if it doesn't find collections folder in zookeeper. On Thu, Jan 10, 2019, 6:32 PM Chris Ulicny Out of curiosity, why are you manually deleting nodes in zookeeper? > > It's always seemed to me that th

Re: Solr Cloud wiping all cores when restart without proper zookeeper directories

Out of curiosity, why are you manually deleting nodes in zookeeper? It's always seemed to me that the majority (definitely not all) of modifications needed during normal operations can usually be done through Solr's APIs. Thanks, Chris On Thu, Jan 10, 2019 at 12:04 AM Yogendra Kumar Soni < yogen

Re: Solr Cloud wiping all cores when restart without proper zookeeper directories

I have an existing collection http://10.2.12.239:11080/solr/test/select?q=*:*&rows=0 { "responseHeader":{ "zkConnected":true, "status":0, "QTime":121, "params":{ "q":"*:*", "rows":"0"}}, "response":{"numFound":150,"start":0,"maxScore":1.0,"docs":[] }} ls ls data?

Re: Solr Cloud wiping all cores when restart without proper zookeeper directories

We've seen the same thing on solr 7.5 by doing: - create a collection - add some data - stop solr on all servers - delete all contents of the solr node from zookeeper - start solr on all nodes - create a collection with the same name as in the first step When doing this, solr wipes out the p

Re: Solr Cloud wiping all cores when restart without proper zookeeper directories

Solr doesn't just remove directories, this is very likely something in your environment that's doing this. In any case, there's no information here to help diagnose. You must tell us _exactly_ what steps you take in order to have any hope of helping. Best, Erick On Wed, Jan 9, 2019 at 2:48 AM Yo

Re: Solr Cloud: Zookeeper failure modes

Right, don't quite know what I was thinking about. Even so, if ZooKeeper is gone you'd still have to rebuild the .system collection too. Or at least figure out how to access it again. On Wed, Jan 2, 2019 at 10:21 AM Gus Heck wrote: > > I thought jar files for custom code were meant to go into the

Re: Solr Cloud: Zookeeper failure modes

I thought jar files for custom code were meant to go into the '.system' collection, not zookeeper. Did I miss a new/old storage option? On Wed, Jan 2, 2019, 12:25 PM Erick Erickson 1> no. At one point, this could be done in the sense that the > collections would be reconstructed, (legacyCloud) bu

Re: Solr Cloud: Zookeeper failure modes

1> no. At one point, this could be done in the sense that the collections would be reconstructed, (legacyCloud) but that turned out to have.. side effects. Even in that case, though, Solr couldn't reconstruct the configsets. (insert rant that you really must store your configsets in a VCS system so

  1   2   3   4   5   6   7   8   9   >