lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amit Nithian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-4471) Replication occurs even when a slave is already up to date.
Date Mon, 25 Feb 2013 17:26:21 GMT

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

Amit Nithian commented on SOLR-4471:
------------------------------------

I'm curious about something. What does:
1) http://localhost:17045/solr/replication?command=indexversion yield
2) http://localhost:<your slave port>/solr/replication?command=details yield

I have noticed that what you see on the UI vs what you see in the indexversion and details
sometimes differ and I wonder if that is a culprit here? Does #1,#2 jive with the versions
that you see in the UI?
                
> Replication occurs even when a slave is already up to date.
> -----------------------------------------------------------
>
>                 Key: SOLR-4471
>                 URL: https://issues.apache.org/jira/browse/SOLR-4471
>             Project: Solr
>          Issue Type: Bug
>          Components: replication (java)
>    Affects Versions: 4.1
>            Reporter: Andre Charton
>            Assignee: Mark Miller
>              Labels: master, replication, slave, version
>             Fix For: 4.2, 5.0
>
>         Attachments: SOLR-4471.patch, SOLR-4471.patch, SOLR-4471.patch, SOLR-4471_TestRefactor.diff,
SOLR-4471_Tests.patch
>
>
> Scenario: master/slave replication, master delta index runs every 10 minutes, slave poll
interval is 10 sec.
> There was an issue SOLR-4413 - slave reads index from wrong directory, so slave is full
copy index from master every time, which is fixed after applying this patch from 4413 (see
script below).
> Now on replication the slave downloads only updated files, but slave is create a new
segement file and also a new version of index (generation is identical with master). On next
polling the slave is download the full index again, because the new version slave is force
a full copy.
> Problem is the new version of index on the slave after first replication.
> {noformat:apply patch SOLR-4413 script, please copy patch into patches directory before
useage.}
> mkdir work
> cd work
> svn co http://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_4_1/
> cd lucene_solr_4_1
> patch -p0 < ../../patches/SOLR-4413.patch
> cd solr
> ant dist
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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


Mime
View raw message