Here's another sequence of messages I frequently see where replication isn't happening with no clearly identified cause:
INFO org.apache.solr.handler.SnapPuller; Starting replication process INFO org.apache.solr.handler.SnapPuller; Master's generation: 6 INFO org.apache.solr.handler.SnapPuller; Slave's generation: 1 INFO org.apache.solr.handler.SnapPuller; Starting replication process INFO org.apache.solr.handler.SnapPuller; Number of files in latest index in master: 94 ERROR org.apache.solr.handler.SnapPuller; No files to download for index generation: 6 This frequently happens with a new slave, so it's never able to get any data for the core. This doesn't normally happen for *all* cores; at least one core will replicate successfully (and continues to stay up to date). I don't think I've seen this with multiple deployments of single-core Solr instances in a container, but it seems odd that multi-core configurations would face as many replication problems as I've seen unless I'm configuring something incorrectly. Are others having better success with multi-core master/slave configurations? Or is this not a well-supported approach to configuration? -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "A storm broke loose in my mind." --Albert Einstein
