[
https://issues.apache.org/jira/browse/SOLR-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583207#comment-13583207
]
Mark Miller commented on SOLR-4482:
-----------------------------------
I think SOLR-4413 fixes this and this dupes SOLR-4471
> SOLR 4.1 replication keeps downloading entire index from master
> ---------------------------------------------------------------
>
> Key: SOLR-4482
> URL: https://issues.apache.org/jira/browse/SOLR-4482
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
> Affects Versions: 4.1
> Environment: Ubuntu Linux
> Reporter: Helder Sepulveda
> Labels: replication, solr
>
> After upgrading to SOLR 4.1 replication keeps downloading entire index from
> master, hardware still the same.
> I do not issue optimize on the master
> The Merge factor is = 6
> Tried both options in the useCompoundFile, same results.
> Been looking at how files are updated in the master, I do:
> http://host:port/solr/replication?command=indexversion
> and the result is:
> {quote}
> <response>
> <lst name="responseHeader">
> <int name="status">0</int>
> <int name="QTime">0</int>
> </lst>
> <long name="indexversion">1361427997259</long>
> <long name="generation">36967</long>
> </response>
> {quote}
> after a commit I see it changes to:
> {quote}
> <response>
> <lst name="responseHeader">
> <int name="status">0</int>
> <int name="QTime">0</int>
> </lst>
> <long name="indexversion">1361428018517</long>
> <long name="generation">36968</long>
> </response>
> {quote}
> Any tips on how to further debug this?
--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
