On 11/4/2014 12:23 PM, Greg Solovyev wrote: > Thanks for the answers Erick. I can see that this is a significant effort and > I am certainly not asking the community to undertake this work. I was > actually going to take a stab at it myself. Regarding $$ savings from not > requiring ZK my assumption is that ZK in production demands a dedicated host > and requires 2GB RAM/instance while Consul runs on less than 100MB > RAM/instance. So, for ISPs, BSP and large enterprise deployments, the savings > come would from reduced resource requirements.
I have a small SolrCloud install. Three servers, two of which run Solr 4.2.1. All three of them run zookeeper. The zookeeper process running on the first Solr server has been running for a long time - started over a year ago on May 6 12:05:37 2013. I forced a full garbage collection on the process and then checked heap usage ... it's less than 50MB. Linux shows a resident size of 200MB, but I could probably decrease that by starting with the -Xmx option. That option is currently not used, so it's accepting Java's defaults. Zookeeper's resource requirements are very small and do not require dedicated hardware. It is a good idea to put the ZK database on separate disk platters from Solr's data, but I'm not even doing that -- everything's on the same filesystem. Thanks, Shawn
