bq: Am I right in saying managed resources are handled by zookeeper rather than files on the filesystem....
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". You can run Solr just like you always have in master/slave setups. In that case you need to manage your own configurations on every node just like you always have, probably through replication. In stand-alone mode, you should send all your managed schema API calls to the master core and let the replication distribute the changes to the slaves. Best, Erick On Wed, Aug 3, 2016 at 4:48 AM, rosbaldeston <rosbaldes...@hotmail.com> wrote: > Am I right in saying managed resources are handled by zookeeper rather than > files on the filesystem and I should ignore any files such as: > managed-schema, _rest_managed.json, > _schema_analysis_stopwords_english.json, > _schema_analysis_synonyms_english.json ... > > I should not try to copy any of these via the slaves confFiles option? > > What I was planning to do was have the master as the indexing source and all > slaves as query sources. But they need the same synonyms & stopwords. > > One thing I am seeing is when I create my master and slave from a custom > configset without any copying of configs is when the masters synonyms have > been changed the synonyms on the slave don't reflect these changes even > sometime after after replication? > > It appears I need to reload the slave core(s) before they show the same > synonyms as the master? is this because they're sharing the same file? how > do should I keep slaves in sync with managed resources? do I just have to > keep reloading all slave cores ever so often? > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Replication-with-managed-resources-tp4289880p4290177.html > Sent from the Solr - User mailing list archive at Nabble.com.
