[
https://issues.apache.org/jira/browse/SOLR-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677954#comment-13677954
]
Noble Paul commented on SOLR-4703:
----------------------------------
I'm assuming that this may not be a common case in production. Yes, the master
and slave can be of different versions during a rollout of new version but it
is just for a small time frame.
SnapPuller never passes the version info to master . It has never been a
problem
> 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 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]
