Linux Zookeeper cluster FAQs and Solutions

The problems mentioned in this article are the integration of problems encountered by others and the collection of other problems.

Question one:

Start Error:

Solution:

1. See if the system firewall is turned off

If turned on, close

2. cause: The zookeeper is started on only one node, the other node does not start the zookeeper, it will cause the connection to be refused, the other node can be started.

3. Delete or comment The 127.0.0.1 line of the Linux Hosts file

Cause: The address of the port binding is not 127.0.0.1 so this address cannot be used

Question two:

Premise: Use the zookeeper version of 3.5.4 BETA,JDK version 1.8

Start Error:

Solution:

Specifying the JDK path in the Zookeeper configuration file Runtime environment

Question three:

Start Error:

Solution:

Configuring Jdk+zookeeper Environment variables (zookeeper environment variables can be ignored)

Question four:

Start Error:

、

Solution:

Check the Zoo.cfg file to the DataDir path to the existence of extra space, if there is a zookeeper read this profile will be read in the file name, so that the corresponding directory is not found, the PID file exists under the specified folder, so cannot find

Question five:

Start Error:

Solution:

This may be because the JDK version of the server is incorrect, or the environment variable is not set.

For example, the original Linux is already installed jdk-1.4, and then install a new version of jdk-1.6, we follow the online tutorial steps to install the zookeeper and set the environment variables, but with the java-version command found that The java-1.4 is still displayed, stating that the environment variables are not well-equipped. The JDK version read by Zookeeper is still an older version of jdk-1.4.

Modify the JDK environment variable configuration

Question six:

Start Error:

Solution:

This exception is usually caused by the fact that Port 2181 is already occupied by other processes.

It is common practice to check which process on the current machine is occupying this port, confirm the necessity of its port occupancy, stop the process, and start zookeeper again.

You can also modify the configuration file Zoo.cfg, replacing the zookeeper ClientPort configuration, for example, you can set it to 2081

Issue seven (multi-Problem collection):

Start Error:

Solution:

Indicates that myid this file does not exist into the/export/servers/data/zookeeper/directory created myID this file (not a folder)

Solution:

In the myID file, enter the Coo.cfg profile that corresponds to the current IP address myID if the current node is configured in the Coo.cfg profile server.1=192.168.1.110:2888:3888 then in the myID file enter 1, save exit

Solution:

Turn off the firewall (firewall for all nodes)

Cause: Zookeeper is started on only one node, the other node does not start zookeeper, which causes the connection to be refused, and the other node can be started.

Linux Zookeeper cluster FAQs and Solutions