[ https://issues.apache.org/jira/browse/SOLR-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602536#action_12602536 ]
Noble Paul commented on SOLR-561: --------------------------------- The next step is to replicate files in conf folder. Thre strategy is as follows, * Mention the files to be replicated from the master, in the _ReplicationHandler_ {code:xml} <requestHandler name="/replication" class="solr.ReplicationHandler" > <str name="confFiles">schema.xml,stopwords.txt,elevate.xml</str> </requestHandler> {code} * For the CMD_FILE_LIST command response include these files also * The slave can compare the files with its local copy and if it is modified download them * If a conf file is changed the the SolrCore must be reloaded * There must be separate strategies for reloading core for single core or multicore > Solr replication by Solr (for windows also) > ------------------------------------------- > > Key: SOLR-561 > URL: https://issues.apache.org/jira/browse/SOLR-561 > Project: Solr > Issue Type: New Feature > Components: replication > Affects Versions: 1.3 > Environment: All > Reporter: Noble Paul > Attachments: SOLR-561.patch, SOLR-561.patch > > > The current replication strategy in solr involves shell scripts . The > following are the drawbacks with the approach > * It does not work with windows > * Replication works as a separate piece not integrated with solr. > * Cannot control replication from solr admin/JMX > * Each operation requires manual telnet to the host > Doing the replication in java has the following advantages > * Platform independence > * Manual steps can be completely eliminated. Everything can be driven from > solrconfig.xml . > ** Adding the url of the master in the slaves should be good enough to enable > replication. Other things like frequency of > snapshoot/snappull can also be configured . All other information can be > automatically obtained. > * Start/stop can be triggered from solr/admin or JMX > * Can get the status/progress while replication is going on. It can also > abort an ongoing replication > * No need to have a login into the machine > This issue can track the implementation of solr replication in java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.