[
https://issues.apache.org/jira/browse/SOLR-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588450#comment-13588450
]
Mark Miller commented on SOLR-4471:
-----------------------------------
{quote}
When I do http://localhost:17045/solr/replication?command=indexversion response
is:
<long name="generation">29037</long>
That's the same version than slaves have, but on the UI generation in master is
now 29082.
{quote}
Sounds like perhaps that needs it's own new JIRA issue?
> 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: [email protected]
For additional commands, e-mail: [email protected]
