ZOOKEEPER in English translation

• zookeeper

Examples of using Zookeeper in Chinese and their translations into English

与标准文件系统不同，ZooKeeper命名空间中的每个节点都可包含与之关联的数据以及孩子。
Unlike is standard file systems, each node in a ZooKeeper namespace can have data associated with it as well as children.

ApacheZooKeeper,ZooKeeper,Apache,Apachefeather标志，ApacheZooKeeper项目标志是Apache软件基金会的商标。
Apache ZooKeeper, ZooKeeper, Apache, the Apache feather logo, and the Apache ZooKeeper project logo are trademarks of The Apache Software Foundation.

字节数组的详细格式特定于具体的应用，而且ZooKeeper不直接提供对它的解析支持。
The exact format of the byte array is specific to each application, and ZooKeeper does not directly provide support to parse it.

支持自动分发索引进程和查询，ZooKeeper提供故障转移和负载平衡。
There is support for distributing both the index process and the queries automatically, and ZooKeeper provides failover and load balancing.

你还将了解Zookeeper是什么，它如何帮助监控集群，为什么HBase使用Zookeeper。
You will also learn what Zookeeper is all about, how it helps in monitoring a cluster, why HBase uses Zookeeper.

它提供对Hadoop生态系统中许多工具的支持，包括Hive、HBase、Pig、Spooq和ZooKeeper。
It offers support for many of the tools in the Hadoop ecosystem including Hive, HBase, Piq, Sqoop and Zookeeper.

使用docker镜像方式在3台服务器上运行zookeeper，使用内网IP，网络模式指定为host；.
Use the docker image to run zookeeper on 3 servers, use Intranet IP, and the network mode is designated as host.

控制器故障转移自动发生，但需要新控制器在初始化期间从ZooKeeper读取每个分区的一些元数据。
The controller failover happens automatically, but requires the new controller to read some metadata for every partition from ZooKeeper during initialization.

该模块显示Kafka集群信息和Zookeeper集群信息，包含如下内容：.
This module displays the Kafka cluster information and the ZooKeeper cluster information, including the following.

ZooKeeper背后的动机是减轻分布式应用程序从头开始实施协调服务的责任。
The motivation behind ZooKeeper is to relieve distributed applications the responsibility of implementing coordination services from scratch.

除了“RequestProcessor”，构成Zookeeper服务的所有服务器都会复制一份这些组件的拷贝。
With the exception of the request processor, each of the servers that make up the ZooKeeper service replicates its own copy of each of components.

在应用程序层面，借助各种存储（如ZooKeeper、FileSystem或Key/Value存储）能够很容易地跟踪Reader的位置。
Tracking reader positions could easily be done at the application level using various stores(such as ZooKeeper, the filesystem, or key-value stores).

它涉及在ZooKeeper中为每个受影响的分区读取和写入一些元数据。
It involves reading and writing some metadata for each affected partition in ZooKeeper.

Kafka在Zookeeper中存储基本元数据，例如有关主题，经纪人，消费者偏移量（队列读者）等的信息。
Kafka stores basic metadata in Zookeeper such as information about topics, brokers, consumer offsets(queue readers) and so on.

每个客户端机器与ZooKeeper服务器之一通信以检索和更新其同步信息。
Each client machine communicates with one of the ZooKeeper servers to retrieve and update its synchronization information.

Zookeeper服务运行所在的服务器集群称作“整体（ensemble）”。
The cluster of servers that the Zookeeper service runs on is called an“ensemble.”.

如果目前现役NameNode崩溃，另一个节点可能从ZooKeeper获得特殊的排外锁以表明它应该成为现役NameNode。
If the current active NameNode crashes, another node can take a special exclusive lock in ZooKeeper indicating that it should become the next active NameNode.

主要以ZooKeeper、Redis、Kafka、MongoDB等应用容器化在Kubernetes平台上面实践。
The main application of ZooKeeper, Redis, Kafka, MongoDB and other application containers on the Kubernetes platform is practiced.

客户端在屏障节点上调用ZooKeeperAPIexists()，watch设置为true.
Client calls the ZooKeeper API's exists() function on the barrier node, with watch set to true.

只要大部分服务器可用，ZooKeeper服务就可用。
As long as most of the servers are available, the Zookeeper service will be available.