|
<< Click to Display Table of Contents >> Zookeeper Requirements |
  
|
|
<< Click to Display Table of Contents >> Zookeeper Requirements |
|
VooltDB deployment supports both single-node and cluster deployment methods. Using cluster deployment can improve the system's high availability capabilities. If you deploy a VooltDB cluster, you need to deploy a set of available ZooKeeper clusters in advance to manage and schedule each VooltDB node.
The Zookeeper version requires 3.4.9 and above. It is recommended to reserve more than 100G of space for a single Zookeeper installation directory. Zookeeper has higher requirements for hardware I/O, and it is recommended to use solid state drives to deploy separately. The planning and deployment of the ZooKeeper cluster is recommended to meet the high availability of Zookeeper and deploy an odd number of servers. VooltDB needs to use an independent Zookeeper cluster to provide services for VooltDB. It is recommended not to share the Zookeeper cluster with other services.
For the stable and efficient operation of the VooltDB cluster, the following configuration items need to be added to the Zookeeper configuration file zoo.cfg:
Configuration Item |
Value |
Description |
autopurge.purgeInterval= |
1 |
Set how many hours to clean up the interaction log. |
autopurge.snapRetainCount= |
10 |
Zookeeper will also save the data in the memory as a snapshot, this configuration can set how many snapshots to keep. |
snapCount= |
3000000 |
After every snapCount transaction log output, a snapshot is triggered. At this time, ZK will generate a snapshot.* file and create a new transaction log file log.*. The default is 100000. |
leaderServes= |
yes |
By default, Leader will accept client connections and provide normal read and write services. However, if you want the Leader to focus on the coordination of machines in the cluster, you can set this parameter to no, which will greatly improve the performance of write operations. |
standaloneEnabled= |
false |
Zookeeper uses cluster mode. |
maxSessionTimeout= |
60000000 |
Session timeout limit. |
preAllocSize= |
131072 |
Pre-open up disk space for subsequent writing to the transaction log. |
tickTime= |
10000 |
A unit of time in ZK. All time in ZK is based on this time unit and is configured in integer multiples. |
syncLimit= |
10 |
During operation, Leader is responsible for communicating with all machines in the ZK cluster, for example, through some heartbeat detection mechanisms to detect the survival status of the machines. If L sends a heartbeat packet after syncLimit, but has not received a response from F, then it is considered that F is no longer online. |
initLimit= |
10 |
During the startup process, the Follower will synchronize all the latest data from the Leader, and then determine the starting state of its external service. |