[
https://issues.apache.org/jira/browse/SOLR-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734464#action_12734464
]
Noble Paul commented on SOLR-1304:
----------------------------------
bq.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..
I suggested one change in the master because it would make the configuration
simpler (only one place) and it must cover most of the use cases . We may not
need more flexibility unless we have usecases to support this.
bq.It'd be nice to be able to have various (and custom) triggers that indicate
the need and what to replicate.
currently the trigger is the change in the file's timestamp. So if you wish
that your file should be replicated , just 'touch' the file (or overwrite it)
and it becomes a candidate for replication.
> 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.
