I'm trying out the replication features on 1.4 (trunk) with multiple indices using a setup based on the example multicore config.
The first time I tried it, (replicating through the admin web interface), it worked fine. I was a little surprised that telling one core to replicate caused both to replicate since the docs seem to imply that replication is done on a per-core basis, but I was happy to see that it worked. I wanted to replay my steps, so on the slave machine I deleted core0/data/* and core1/data/* and restarted the server. I restarted the server on master just to be sure. Now replication doesn't work at all. I've tried it both through the admin interface and by curl: curl http://localhost:8983/solr/core0/replication?command=snappull The response from curl indicates that the replication was successful, but nothing happened; my slave index is still empty. My only guess as to what's going wrong here is that deleting the coreN/data directory is not a good way to "reset" a core back to its initial condition. Maybe there's a bit of state somewhere that's making the slave think that it's already up-to-date with this master and so it doesn't need to do any replicating? But this is a wild conjecture; I'd appreciate any tips on where to look for what's going wrong. As to why the replication claims to be successful, I've no idea. Am I missing some crucial log file that explains what's going wrong? It's also possible that this stuff is still in a heavy state of development such that it shouldn't be expected to work by casual users, if that is the case I can go back to the external-script-based replication features of 1.3. thanks, Phil Hagelberg http://technomancy.us
