Okay one last note... just for closure... looks like it was addressed in solr 4.1+ (I was looking at 4.0).
On Thu, Jan 24, 2013 at 11:14 PM, Amit Nithian <anith...@gmail.com> wrote: > Okay so after some debugging I found the problem. While the replication > piece will download the index from the master server and move the files to > the index directory but during the commit phase, these "older" generation > files are deleted and the index is essentially left in tact. > > I noticed that a full copy is needed if the index is "stale" (meaning that > files in common between the master and slave have different sizes) but also > I think a full copy should be needed if the slaves generation is higher > than the master as well. In short, to me it's not sufficient enough to > simply say a full copy is needed if the slave's index version is >= > master's index version. I'll create a patch and file a bug along with a > more thorough writeup of how I got in this state. > > Thanks! > Amit > > > > On Thu, Jan 24, 2013 at 2:33 PM, Amit Nithian <anith...@gmail.com> wrote: > >> Does Solr's replication look at the generation difference between master >> and slave when determining whether or not to replicate? >> >> To be more clear: >> What happens if a slave's generation is higher than the master yet the >> slave's index version is less than the master's index version? >> >> I looked at the source and didn't seem to see any reason why the >> generation matters other than fetching the file list from the master for a >> given generation. It's too wordy to explain how this happened so I'll go >> into details on that if anyone cares. >> >> Thanks! >> Amit >> > >
