Sounds good I am trying the combination of my patch and 4413 now to see how it works and will have to see if I can put unit tests around them as some of what I thought may not be true with respect to the commit generation numbers.
For your issue above in your last post, is it possible that there was a commit on the master in that slight window after solr checks for the latest generation of the master but before it downloads the actual files? How frequent are the commits on your master? On Thu, Feb 21, 2013 at 2:00 AM, raulgrande83 <raulgrand...@hotmail.com>wrote: > Thanks for the patch, we'll try to install these fixes and post if > replication works or not. > > I renamed 'index.<timestamp>' folders to just 'index' but it didn't work. > These lines appeared in the log: > INFO: Master's generation: 64594 > 21-feb-2013 10:42:00 org.apache.solr.handler.SnapPuller fetchLatestIndex > INFO: Slave's generation: 64593 > 21-feb-2013 10:42:00 org.apache.solr.handler.SnapPuller fetchLatestIndex > INFO: Starting replication process > 21-feb-2013 10:42:00 org.apache.solr.handler.SnapPuller fetchFileList > SEVERE: No files to download for index generation: 64594 > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Slaves-always-replicate-entire-index-Index-versions-tp4041256p4041827.html > Sent from the Solr - User mailing list archive at Nabble.com. >
