The ZooKeeper Import/Export API provides methods to upload or download information from
Fusion’s ZooKeeper service.
This service provides an alternative to the ZooKeeper clients zkCli.sh and zk-shell which are part of
the Apache Zookeeper distribution included as part of the Fusion distribution.
It was introduced as part of the Fusion 2.0 release.

The ZKImportExport service may be used to export ZooKeeper data for any Fusion release.
It can be used to import configuration data into the ZooKeeper service for a
new or existing Fusion deployment. Note that since the Fusion 3.0 release all ZooKeeper paths vary according to the version of Fusion that you are running.

For details on using this script during the Fusion upgrade procedure, see
Upgrading Fusion.

For details on using this script to migrate Fusion configurations from one deployment to another, see
Migrating Fusion data.

The REST API only supports requests to export ZooKeeper configurations.
The Fusion distribution includes a utility script zkImportExport.sh which
can be used to import ZooKeeper configuration as well as to export it from
arbitrary Fusion instances.

ZooKeeper

Apache ZooKeeper is a distributed configuration service, synchronization service, and naming registry.
Fusion uses ZooKeeper to configure and manage all Fusion components in a single Fusion deployment.

znode: ZooKeeper data is organized into a hierarchal name space of data nodes called znodes.
A znode can have data associated with it as well as child znodes.
The data in a znode is stored in a binary format, but it is possible to import, export, and view this information as JSON data.
Paths to znodes are always expressed as canonical, absolute, slash-separated paths; there are no relative reference.

ephemeral nodes: An ephemeral node is a znode which exists only for the duration of an active session.
When the session ends the znode is deleted. An ephemeral znode cannot have children.

server: A ZooKeeper service consists of one or more machines; each machine is a server which runs in its own JVM and listens on its own set of ports.
For testing, you can run several ZooKeeper servers at once on a single workstation by configuring the ports for each server.

quorum: A quorum is a set of ZooKeeper servers. It must be an odd number. For most deployments, only 3 servers are required.

client: A client is any host or process which uses a ZooKeeper service.