[
https://issues.apache.org/jira/browse/SOLR-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734334#action_12734334
]
Otis Gospodnetic commented on SOLR-1304:
----------------------------------------
Would it make more sense for the caller to specify (in the request) which files
to replicate, thus giving it full control over what to replicate when? Maybe
the "realTimeConfFiles" should then not list all conf files that should always
be replicated, but instead list all the conf files that are *allowed* to be
replicated when the caller request some of them to be replicated?
> 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.
