0

I'm considering using Zookeeper to manage shared configuration across multiple services that live on a single application server. Usage would be very low volume, mostly reads. My production system uses 2 VMs: one application server and one database server.

Zookeeper docs suggest that, in production, you want an ensemble of at least 3 instances.

I have two obvious options:

  1. Install two Zookeeper instances on one of the two VMs, and one on the other.
  2. Use only one Zookeeper instance.

If I only use one instance, and I can live with some downtime if Zookeeper happens to go down (which I would hope only occurs rarely), are there serious risks with only using one instance? When maintaining the server I'd be bringing Zookeeper down regardless.

There is the possible issue of file corruption in the data folder. Are additional instances required to recover in this scenario? Or can one simply delete the most recent snapshot and fall back to the previous one (with possible data loss)?

Can anyone speak to the risks involved? How bad an idea is this?

Remi Despres-Smyth
  • 141
  • 8
  • Does this answer your question? [Can you help me with my capacity planning?](https://serverfault.com/questions/384686/can-you-help-me-with-my-capacity-planning) – djdomi Apr 21 '22 at 17:15
  • @djdomi No. My question isn't related to capacity or capacity planning; a single server would have plenty of resources for the use I'm going to put it to. But if I run Zookeeper on a single server - against their recommendations - there are certainly risks to that. I'm looking for info regarding what those risks are. – Remi Despres-Smyth Apr 21 '22 at 18:12
  • but even that, opinion based questions are also off topic ;) – djdomi Apr 22 '22 at 03:50
  • @djdomi Not looking for opinions, looking for people familiar with the project who can tell me what can go wrong if this is done. I would hope possible failure modes to be known to people who know the project well. – Remi Despres-Smyth Apr 22 '22 at 12:01

0 Answers0