One more tidbit: I just tried leaving replication off for a few hours and then triggering a "big" replication run so I could see the distinct stages.
- Beginning replication didn't cause any performance degradation. - Several minutes of downloading the replication files saw no degradation - Only after downloading had completed did we start to see performance issues in our tests - But we saw the "number of docs/timestamp of latest file" both jump almost immediately after downloading completed and never move again - But the performance degradation continued for about seven more minutes even though replication was clearly finished at this point Is there some kind of re-indexing optimization thing that solr can run post-replication? At this point it's about my only remaining suspect..
