Not that I know of, but.... look before you leap. I took a quick look at Consul and it really doesn't look like any kind of drop-in replacement. Also, the Zookeeper usage in SolrCloud isn't really pluggable AFAIK, so there'll be lots of places in the Solr code that need to be reworked etc., especially in the realm of collections and sharding.
The Collections API will be challenging to port over I think. Not to mention SolrJ and CloudSolrServer for clients who want to interact with SolrCloud through Java. Not saying it won't work, I just suspect that getting it done would be a big job, and thereafter keeping those changes in sync with the changing SolrCloud code base would chew up a lots of time. So if I were putting my Product Manager hat on I'd ask "is the benefit worth the effort?". All that said, go for it if you've a mind to! Best, Erick On Fri, Oct 31, 2014 at 4:08 PM, Greg Solovyev <g...@zimbra.com> wrote: > I am investigating a project to make SolrCloud run on Consul instead of > ZooKeeper. So far, my research revealed no such efforts, but I wanted to > check with this list to make sure I am not going to be reinventing the wheel. > Have anyone attempted using Consul instead of ZK to coordinate SolrCloud > nodes? > > Thanks, > Greg
