disaster recovery scenarios for solr cloud and zookeeper
Hi, Solr 4.x is architected with a dependency on Zookeeper, and Zookeeper is expected to have a very high (perfect?) availability. With 3 or 5 zookeeper nodes, it is possible to manage zookeeper maintenance and online availability to be close to %100. But what is the worst case for Solr if for some unanticipated reason all Zookeeper nodes go offline? Could someone comment on a couple of possible scenarios for which all ZK nodes are offline. What would happen to Solr and what would be needed to recover in each case? 1) brief interruption, say 2 minutes, 2) longer downtime, say 60 min Thanks Dennis
Solr URL uses non-standard format with pound sign
The Solr URL in Solr 4.2 for my localhost installation looks like this: http://localhost:8883/solr/#/development_shard1_replica1 This URL when constructed dynamically in Ruby will not validate with the Ruby URI:HTTP class because of the # sign in the path. This is a non-standard URL as per RFC1738. Here is the error message: #URI::InvalidComponentError: bad component(expected absolute path component): /solr/#/development_shard1_replica1 Is there another way to access the Solr URL without using the # sign? Thanks, Dennis Haller
