This repository has been archived by the owner on Apr 23, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 444
Home
Jordan Zimmerman edited this page Jul 20, 2015
·
18 revisions
Use links at right -———>
According to the ZooKeeper documentation
You will want to have a supervisory process that manages each of your ZooKeeper server processes (JVM).
Exhibitor is a Java supervisor system for ZooKeeper. It provides a number of features:
- Watches a ZK instance and makes sure it is running
- Performs periodic backups
- Perform periodic cleaning of ZK log directory
- A GUI explorer for viewing ZK nodes
- A rich REST API
- It’s assumed that you are familiar with ZooKeeper and the basics of administering it (see the ZooKeeper Administrator’s Guide for details).
- Exhibitor is a Java-based application
- Exhibitor is designed to be run on Unix/Linux based systems (as is Apache ZooKeeper).
- The java CLI tool
jps
must be in the command line PATH.
- Exhibitor manages your zoo.cfg and myid files. Do not edit these manually as Exhibitor will overwrite them.
- In addition to the standard ZooKeeper ports, your firewall must have Exhibitor’s HTTP port open as each Exhibitor instance communicates with the others for status.
Exhibitor binaries are published to Maven Central.
GroupID/Org | ArtifactID/Name | Description |
---|---|---|
com.netflix.exhibitor | exhibitor-standalone | Self-containing, runnable version of Exhibitor (as an application or a WAR file) |
com.netflix.exhibitor | exhibitor-core | Library version of Exhibitor that can be integrated into your application |
Contents
- Top
- Standalone Version
- WAR File
- Core/Library
- Features
- Shared Configuration
- Using Exhibitor
- REST API
- Contributions