lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Henson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-820) replicate After startup for new replication
Date Tue, 13 Jan 2009 23:24:59 GMT

    [ https://issues.apache.org/jira/browse/SOLR-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663533#action_12663533
] 

Michael Henson commented on SOLR-820:
-------------------------------------

I have not been able to get this to work in my configuration. The slave instance, starting
with an empty target directory, creates segments files for itself on startup. It then has
an "index version" that is a higher number than the master's index version. The replication
never starts, unless I do a commit on the master.

My replication config is very straightforward. My configuration assumes that the slave machine
is starting off completely empty of all data (aside from the essentials necessary to get Solr
to start), and will pull everything from the master instance.


> replicate After startup for new replication
> -------------------------------------------
>
>                 Key: SOLR-820
>                 URL: https://issues.apache.org/jira/browse/SOLR-820
>             Project: Solr
>          Issue Type: Improvement
>          Components: replication (scripts)
>            Reporter: Noble Paul
>            Assignee: Shalin Shekhar Mangar
>            Priority: Minor
>             Fix For: 1.4
>
>         Attachments: SOLR-820.patch
>
>
> add another option of 
> {code}
>  <str name="replicateAfter">startup</str>
> {code}
> so that replication can be triggered w/o a commit

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message