bq: I'm also guessing those _schema and managed_schema files are an implementation detail for the missing zookeeper functionality. But if I did add those to a conffiles option it might automate the slave core reloads for me?
You're getting closer ;). There's nothing Cloud specific about the whole managed schema functionality, although that is where it's gotten the most exercise so.... So if you're saying that you change the managed schema file on the master and it is _not_ replicated automatically to the slave (you'll have to have added docs I believe on the master, I don't think replication happens just because of config changes) then I think that's worth a JIRA, can you please confirm? So if this sequence doesn't work: 1> change the managed schema 2> index some docs 3> wait for a replication 4> the managed schema file on the slave has _not_ been updated then please raise a JIRA. Make sure you identify that this is stand-alone. NOTE: I'm not sure what the right thing to do in this case is, but the JIRA would allow a place to discuss what "the right thing" would be. In the meantime, you should be able to work around that by explicitly listing them in the conffiles section. Best, Erick On Wed, Aug 3, 2016 at 8:58 AM, rosbaldeston <rosbaldes...@hotmail.com> wrote: > Erick Erickson wrote >> It Depends. When running in Cloud mode then "yes". If you're running >> stand-alone >> then there is no Zookeeper running so the answer is "no". > > Ah that helps, so no zookeeper in my case. I did wonder if it wasn't just > sharing the same config files between master and slave from sharing the same > configset. So it would appear I'm not replicating any of the managed files > and reloading the slave core probably just reread the shared synonyms file. > > I'm also guessing those _schema and managed_schema files are an > implementation detail for the missing zookeeper functionality. But if I did > add those to a conffiles option it might automate the slave core reloads for > me? > > >> If a replication involved downloading of at least one configuration file, >> the ReplicationHandler issues a core-reload command instead of a commit >> command. > > (from https://cwiki.apache.org/confluence/display/solr/Index+Replication) > > Currently I've no conffiles set on the slave and I know it didn't get > reloaded after synonym changes to the master. > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Replication-with-managed-resources-tp4289880p4290242.html > Sent from the Solr - User mailing list archive at Nabble.com.
