[
https://issues.apache.org/jira/browse/SOLR-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600827#action_12600827
]
Shalin Shekhar Mangar commented on SOLR-561:
--------------------------------------------
bq.Re poll interval: I think the HH:MM:ss is enough. Does that allow polling,
say, every 72 hours? Just use 72:00:00, right?
Correct, 72:00:00 will work.
bq.Re Winblows problem: I'd like the switch to the current/latest snapshot, but
this prevents us from always knowing the location of the active directory. We'd
have to rely on sorting the dir with snapshot names and assuming the currently
active index is the one with the most recent snapshot, no? Symlinks would be
great here, but again, Winblows doesn't have them (and I think using shortcuts
for this wouldn't work).
As Noble suggested, once the new searcher is in use and the older one is
closed, hopefully windows will kindly grant us permission to delete the files
in the index directory. We can then create links to the files in the snapshot
being used into the index directory. The latest snapshot directory will be the
active one but we'll know what index is being used through the links in the
index folder.
> 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
>
> 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.
