In the previous blog post about SolrCloud we’ve talked about the situation when ZooKeeper connection failed and how Solr handles that situation. However, we only talked about query time behavior of SolrCloud and we said that we will get back to the topic of indexing in the future. That future is finally here – let’s see what happens to indexing when ZooKeeper connection is not available.
zookeeper
SolrCloud – What happens when ZooKeeper fails?
One of the questions I tend to get is what happens with SolrCloud cluster when ZooKeeper fails. Of course we are not talking about a single ZooKeeper instance failure, but the whole ensemble not being accessible and so the quorum not present. Because the answer to this question is very easy to verify i decided to make a simple blog post to show what happens when ZooKeeper fails.
SolrCloud – What happens when ZooKeeper fails?
One of the questions I tend to get is what happens with SolrCloud cluster when ZooKeeper fails. Of course we are not talking about a single ZooKeeper instance failure, but the whole ensemble not being accessible and so the quorum not present. Because the answer to this question is very easy to verify i decided to make a simple blog post to show what happens when ZooKeeper fails.
SOLR-1873 – Solr Cloud in trunk
A few minutes ago changes marked as SOLR-1873 in the Apache JIRA system were added the trunk branch of Lucene and Solr SVN repository This means that the developer version of Solr was expanded with the functionality called Solr Cloud – the ability of managing the distributed Solr deployment from the administration pages.
We will try to write something about these new functionality as soon as possible 😉