[
https://issues.apache.org/jira/browse/SOLR-9382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407842#comment-15407842
]
Richard osbaldeston commented on SOLR-9382:
-------------------------------------------
A possible improvement could be the ability to use of wildcard globs in
replication conffiles to monitor all language variants of the managed stopwords
& synonyms.
> Replication of managed resources on standalone servers
> ------------------------------------------------------
>
> Key: SOLR-9382
> URL: https://issues.apache.org/jira/browse/SOLR-9382
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: replication (java)
> Affects Versions: 5.5
> Environment: Solr 5.5.1, Centos 6.5, JDK 1.7
> Reporter: Richard osbaldeston
> Labels: configset, managedResource, replication
> Attachments: Capture.GIF
>
>
> I've a single standalone server with a managed schema, synonyms and
> stopwords. I was planning on configuring as master and slave cores via
> replication, the master as the indexing source and all slaves replicated from
> the master as query sources.
> Where I started to run into problems is with the conffiles option on the
> slave replication setup. Because I'm using a shared configset and managed
> resources It wasn't clear how to configure this (no schema.xml or
> synonyms.txt...).
> First I tried with no conffiles , then I tried adding the managed resource
> generated files in conffiles. But the behaviour I'm seeing in both cases was
> no replication of the conffiles (managed resources) is apparently taking
> place? Not on indexing replication, nor manual requests to replicate the
> slave.
> In this case as the conf files are shared, no actual copying needs to take
> place however when synonyms are added to the master via the rest api the
> changes are immediately viewable via the masters synonyms resource. But the
> slave core needs to reloaded before the same changes appear there.
> So what I wanted was the slave core(s) to be reloaded(\?) when config files
> change. Which the index replication documentation suggests should be
> happening?
> {quote}
> If a replication involved downloading of at least one configuration file, the
> ReplicationHandler issues a core-reload command instead of a commit command.
> {quote}
> So this a part bug report and part discussion on how should this work for
> standalone servers?
> ref:
> http://lucene.472066.n3.nabble.com/Replication-with-managed-resources-tp4289880.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
