[
https://issues.apache.org/jira/browse/SOLR-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734359#action_12734359
]
Erik Hatcher commented on SOLR-1304:
------------------------------------
I've been working with replication a bit lately, and first, this Java-based
replication has been a joy to set up and see working.
One use case I've encountered, replicating when the spell check index has been
rebuilt, but the main index remains the same. It'd be nice to be able to have
various (and custom) triggers that indicate the need and what to replicate.
For example, just touching a query-time synonyms.txt file ought to trigger
searchers to pull it (yet this requires a core reload for that file to be
reloaded by SynonymFilterFactory, d'oh)
> Make it possible to force replication of at least some of the config files
> even if the index hasn't changed
> -----------------------------------------------------------------------------------------------------------
>
> Key: SOLR-1304
> URL: https://issues.apache.org/jira/browse/SOLR-1304
> Project: Solr
> Issue Type: Improvement
> Components: replication (java)
> Reporter: Otis Gospodnetic
> Priority: Minor
> Fix For: 1.5
>
>
> From http://markmail.org/thread/vpk2fsjns7u2uopd
> Here is a use case:
> * Index is mostly static (nightly updates)
> * elevate.xml needs to be changed throughout the day
> * elevate.xml needs to be pushed to slaves and solr needs to reload it
> This is currently not possible because replication will happen only if the
> index
> changed in some way. You can't force a commit to fake index change. So one has
> to either:
> * add/delete dummy docs on master to force index change
> * write an external script that copies the config file to slaves
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
