Hi all, me, Upayavira and other guys at Sourcesense have collected some Solr architectural views inside the presentation at [1]. For sure one can set up an architecture for failover and resiliency on the "search face" (search slaves with coordinators and distributed search) but I'd like to ask how would you reach transparent redundancy in Solr on the "index face". On slide 13 we put 2 slave backup masters and so if one of the main masters goes down you can switch slaves' replication on the backup master. First question if how could it be made automatic? In a previous thread [2] I talked about a possible solution writing the master url of slaves in a properties file so when you have to switch you change that url to the backup master and reload the slave's core but that is not automatic :-) Any more advanced ideas? Second question: when main master comes up how can it be automatically considered as the backup master (since hopefully the backup master has received some indexing requests in the meantime)? Also consider that its index should be wiped out and replicated from the new master to ensure index integrity. Looking forward for your feedback, Cheers, Tommaso
[1] : http://www.slideshare.net/sourcesense/sharded-solr-setup-with-master [2] : http://markmail.org/thread/vjj5jovbg6evpmpp
