So Many Zookeeper Warnings--There Must Be a Problem

from another server we get this: These are making our logs impossible to read, but worse, I assume indicate that something is wrong. Thanks for any help! Joe Lerner -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: So Many Zookeeper Warnings--There Must Be a Problem

Hi Scott, First, we are definitely mis-onfigured for the myid thing. Basically two of them were identifying as ID #2, and they are the two ZK's claiming to be the leader. Definitely something to straighten out! Our 3 lines in zoo.cfg look correct. Except they look like this: clientPort:2181 ser

Re: So Many Zookeeper Warnings--There Must Be a Problem

wrt, "You'll probably have to delete the contents of the zk data directory and rebuild your collections." Rebuild my *SOLR* collections? That's easy enough for us. If this is how we're incorrectly configured now: server #1 = myid#1 server #2 = myid#2 server #3 = myid#2 My plan would be to do t

Continuous Zookeeper Client Warnings

, and I assume indicate that something is wrong. Thanks for any help! Joe Lerner -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Warnings in Zookeeper Server Logs

Hi (yes again): We have a simple architecture: 2 SOLR Cloud servers (on servers #1 and #2), and 3 zookeeper instances (on servers #1, #2, and #3). Things appear to work fine, and I have confirmed that our basic configuration is correct. But we are seeing TONS of the following warnings in all of ou

Re: Warnings in Zookeeper Server Logs

After a long slog, I am now able to answer my own question, just in case anybody is listening. We determined that when we deploy our application to Tomcat using the Tomcat deploy service, which happens when we deploy with Jenkins and Ansible, these errors start. Conversely, if we re-start Tomcat

Re: Cannot Figure out Reason for Persistent Zookeeper Warning

Our application runs on Tomcat. We found that when we deploy to Tomcat using Jenkins or Ansible--a "hot" deployment--the ZK log problem starts. The only solution we've been able to find was to bounce Tomcat. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Schema Change for Solr 7.4

We recently set up Solr 7.4 in Production. There are 2 Solr nodes, with 3 zookeepers. We need to make a schema change. What I want to do is simply push the updated schema to Solr, and then re-index all the content to pick up the change. But I am being told that I need to: 1. Delete the collec

Re: Schema Change for Solr 7.4

OK--yes, I can see how that would work. But it would require some quick infrastructure flexibility that, at least to this point, we don't really have. Joe -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Solr Migration to The AWS Cloud

Hi, Our application is migrating from on-premise to AWS. We are currently on Solr Cloud 7.3.0. We are interested in exploring ways to do this with minimal, down-time, as in, maybe one hour. One strategy would be to set up a new empty Solr Cloud instance in AWS, and reindex the world. But reinde

Re: Solr Migration to The AWS Cloud

Ooohh...interesting. Then, presumably there is some way to have what was the cross-data-center replica become the new "primary"? It's getting too easy! Joe -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Error Adding a Replica to SOLR Cloud 8.2.0

We finally got this fixed by temporarily disabling any updates to the SOLR index. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Dynamic starting or stoping of zookeepers in a cluster

This is solid information. *How about the application, which uses SOLR/Zookeeper?* Do we have to follow this guidance, to make the application ZK config aware: https://zookeeper.apache.org/doc/r3.5.5/zookeeperReconfig.html#ch_reconfig_rebalancing