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

Thomas Dudziak commented on SOLR-4703:
--------------------------------------

I have the same problem between a LucidWorks 2.0.1 (I believe Solr 4.0 ?) 
server and a Apache Solr 4.0 slave.
Interestingly documentation states that the filelist command needs indexversion 
and not generation (about half-way through in this document: 
https://cwiki.apache.org/confluence/display/solr/Index+Replication#IndexReplication-IndexReplicationusingsshandrsync
 and this has been the case since at least 4.4) whereas the code in Solr (at 
least for 4.0) in ReplicationHandler#getFileList looks for generation.

> Index Replication Fails between 4.x and 3.x Because SnapPuller doesn't pass 
> indexversion info to Master
> -------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-4703
>                 URL: https://issues.apache.org/jira/browse/SOLR-4703
>             Project: Solr
>          Issue Type: Bug
>          Components: replication (java)
>    Affects Versions: 4.2
>            Reporter: Umesh Prasad
>            Priority: Minor
>              Labels: replication
>         Attachments: solr.replication.fetchFileList.trunk.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Replication Sequence in Solr 4.2 is 
> 1. Get replicable indexVersion & Generation from Master 
> 2. Fetch File list for given indexVersion and Generation from Master
> 3. Down the File list
> Solr 4.2 and trunk have a Bug, whereby Slave doesn't pass the indexVersion to 
> Master. Master, informs the slave that indexVersion param is missing, but 
> slave ignores it and instead says that there are no filelists to down. 
>   And replication breaks.
>   



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to