[jira] [Closed] (SOLR-2678) confFiles replication: Flags for "No-reloadCore" and "No-Backup" for specific files

["Jan Høydahl (JIRA)" <ji...@apache.org>]

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

Jan Høydahl closed SOLR-2678.
-----------------------------
    Resolution: Won't Fix

Closing as won't fix since this has not seen attention in 5 years, and focus has shifted to Cloud. If anyone disagree, feel free to discuss further :)

> confFiles replication: Flags for "No-reloadCore" and "No-Backup" for specific files
> -----------------------------------------------------------------------------------
>
>                 Key: SOLR-2678
>                 URL: https://issues.apache.org/jira/browse/SOLR-2678
>             Project: Solr
>          Issue Type: New Feature
>          Components: replication (java)
>    Affects Versions: 3.3
>            Reporter: Mark Plomer
>            Priority: Minor
>
> It would be nice to have the possibility to specify for some confFiles, if the core should be reloaded when they have changed, and if they should be backed-up when replicating.
> Background: I setup a failover solr server as slave. To have the possibility to switch it to a master server manually, I replicate the dataimport.properties file to have always the corresponding last_index_time for the delta-import in DIH.
> But as this file changes on every new index, of course, the complete core on the slave it reloaded every time which is not neccessary. Also the conf-directory is cluttered up with a lot of unneeded backups of dataimport.properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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