[
https://issues.apache.org/jira/browse/SOLR-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734356#action_12734356
]
Erik Hatcher commented on SOLR-1304:
------------------------------------
I just want to make a strong note about security here. We must be very careful
that replication cannot replicate files outside of solr home or the solr data
directory. And perhaps file list selection capability (includes/excludes)...
hmmm... sounds a lot like Ant to me ;).... be centralized between the
ShowFileRequestHandler and what can be replicated.
assert("no way Jose", /replicate?command=sendfile&file=/etc/passwd)
> 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.
