With our design we end up building out a stand alone zookeeper cluster 3 nodes. 
 Zookeeper seems to be the default dumping ground for many Apache based 
products these days. You will eventually see many services and frameworks 
require a zk instance for leader election, coordination, Kv store etc.. I've 
seen situations where the masters can become extremely busy and cause 
performance problem with Zk which can be huge issue for mesos. 
Sent from Outlook Mobile




On Thu, Dec 24, 2015 at 8:01 AM -0800, "Ron Lipke" <[email protected]> wrote:










Hello, I've been working on setting up a mesos cluster for eventual
production use and I have a question on configuring zookeeper alongside
the mesos masters.  
Is it best practice to run zookeeper/exhibitor as a separate cluster (in
our case, three nodes) or on the same machines as the mesos masters?  I
understand the drawbacks of increased cost for compute resources that
will just be running a single service and most of the reference docs
have them running together, but just wondering if it's beneficial to
have them uncoupled.

Thanks in advance for any input.

Ron Lipke
@neverminding






-- 
*NOTICE TO RECIPIENTS*: This communication is confidential and intended for 
the use of the addressee only. If you are not an intended recipient of this 
communication, please delete it immediately and notify the sender by return 
email. Unauthorized reading, dissemination, distribution or copying of this 
communication is prohibited. This communication does not constitute an 
offer to sell or a solicitation of an indication of interest to purchase 
any loan, security or any other financial product or instrument, nor is it 
an offer to sell or a solicitation of an indication of interest to purchase 
any products or services to any persons who are prohibited from receiving 
such information under applicable law. The contents of this communication 
may not be accurate or complete and are subject to change without notice. 
As such, Orchard App, Inc. (including its subsidiaries and affiliates, 
"Orchard") makes no representation regarding the accuracy or completeness 
of the information contained herein. The intended recipient is advised to 
consult its own professional advisors, including those specializing in 
legal, tax and accounting matters. Orchard does not provide legal, tax or 
accounting advice.

Reply via email to