On 2/15/2017 4:06 AM, philippa griggs wrote: > Solr 5.4.1, multiple cores with two cores per shard. Zookeeper 3.4.6 (5 > zookeeper ensemble). > > I have noticed an error with the replication between two cores in a shard. > I’m having to perform a schema update which means I have to stop and start > the cores. I’m trying to do this in a way so I don’t get any down time. > Restarting one core in the shard, waiting for that to come back up before > restarting the second one.
You're talking about zookeeper, which means SolrCloud. Just reload the collection after you change the config/schema in zookeeper. Solr will handle reloading all shards and all replicas, no matter how many actual servers are involved. There will be no downtime. https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-RELOAD:ReloadaCollection > However when restarting the master, the slave isn’t flipping and becoming the > master itself. Instead I’m getting errors in the log as follows: We would need to see the *full* error in your logs. It looks like you've just pulled part of it out and not included the entire message, which might be dozens of lines. There are no masters and no slaves in normal SolrCloud operation. One of the replicas of each shard gets elected as leader. The replication feature is **NOT** used unless something goes wrong. If a replica requires complete replacement, then SolrCloud will use the old master/slave replication feature to copy the leader's index to the bad replica. > When I run > > http://xxx:8983/solr/core_name/replication?command=details<http://ec2-52-5-236-168.compute-1.amazonaws.com:8987/solr/sessionfilterset/replication?command=details> If you're running SolrCloud (Solr plus zookeeper), why are you doing anything at all with the replication handler? As I said above, SolrCloud only uses the replication feature in emergencies. It doesn't touch the replication handler's config as master or slave until the precise moment that an index replication is actually needed. A core's status as a replication master or slave is meaningless to normal SolrCloud operation. Thanks, Shawn
