[jira] [Updated] (SOLR-1304) Make it possible to force replication of at least some of the config files even if the index hasn't changed

["David Smiley (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Smiley updated SOLR-1304:
-------------------------------

    Fix Version/s:     (was: 4.7)
                   4.8

> 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: 4.8
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org