On 5/3/2013 8:35 AM, Edd Grant wrote: > Thanks, that's exactly what I was worried about. If I take your suggested > approach of using SolrCloudServer and the feeder learns which shard leader > to target, then if the shard leader goes down midway through indexing then > I've lost my ability to index. Whereas if I take the route of making all > updates via the HAProxy instance then I've got HA but at the cost of > performance. > > This has me wondering if it might be feasable to address each shard with a > VIP? Then if the leader of the shard goes down and a replica is elected as > the leader it could also take the VIP, so in essence we'd always be sending > messages to the leader. Anyone tried anything like this?
CloudSolrServer is part of the SolrJ (Java) API. It incorporates a zookeeper client. To initialize it, you don't tell it about your Solr servers, you give it the same zookeeper host information that you give to Solr when starting in cloud mode. It always knows the current state of the cluster, so if you have a failure, it adjusts so that your queries and updates don't fail. That also means that it will know when servers are added to or removed from the cloud. http://lucene.apache.org/solr/4_2_1/solr-solrj/org/apache/solr/client/solrj/impl/CloudSolrServer.html Thanks, Shawn
