Yes - better use of existing resources. In this case, the chroot would be helpful to keep Solr znodes separate from HBase. For the most part, Solr in steady-state doesn't put a lot of stress on Zookeeper, for the most part my zk nodes are snoozing.
On Tue, Apr 23, 2013 at 1:46 PM, Furkan KAMACI <furkankam...@gmail.com> wrote: > If I have a Zookeper Cluster for my Hbase Cluster already, can I use same > Zookeper cluster for my SolrCloud too? > > 2013/4/23 Timothy Potter <thelabd...@gmail.com> > >> Ah cool, thanks for clarifying Chris - some of that multi-config >> management stuff gets confusing but much clearer from your >> description. >> >> Cheers, >> Tim >> >> On Tue, Apr 23, 2013 at 11:36 AM, Chris Hostetter >> <hossman_luc...@fucit.org> wrote: >> > >> > : Yes, you can effectively chroot all the configs for a collection (to >> > : support multiple collections in same ensemble) - see wiki: >> > : http://wiki.apache.org/solr/SolrCloud#Zookeeper_chroot >> > >> > I don't think chroot is suitable for what's being asked about here ... >> > that would completely isolate two cloud clusters from eachother. >> > >> > i believe the intent of the question is asking about having a cloud >> > cluster in which multiple collections exist, and some collections use >> > differnet schema.xml files then other collections >> > >> > the short answer is: absolutely, each collecion can use completley >> > differnet sets of configs (just like in non-cloud mode each core can use >> > distinct configs) but to help make management easier when you have many >> > collections re-using the same set of configs there is the concept of a >> > "config set" ... you can push a set of configs into ZK with a specific >> > "configName", nad then refer to that config set name when creating >> > collections... >> > >> > >> https://wiki.apache.org/solr/SolrCloud#Getting_your_Configuration_Files_into_ZooKeeper >> > >> http://wiki.apache.org/solr/SolrCloud#Managing_collections_via_the_Collections_API >> > >> > >> > -Hoss >>
