ZooKeeper instance is always in the Concerning state.

TingtingGG · Created Jun 29, 2019 10:14:41

Hey there!

Log in to the node where the original malfunctioning ZooKeeper instance resides and run the following command to check the directory.

ls -l /srv/BigData/zookeeper/version-2/.

If the directory is not blank, the instance has been restored.

Example:

-rw------- 1 omm wheel       1 Mar  5 18:24 acceptedEpoch
-rw------- 1 omm wheel       1 Mar  5 18:24 currentEpoch
-rw------- 1 omm wheel 67108880 Mar  5 18:31 log.600000001
-rw------- 1 omm wheel    873 Feb 27 02:47 snapshot.50000000d
-rw------- 1 omm wheel    665 Mar  5 18:13 snapshot.60000001d
-rw------- 1 omm wheel    849 Mar  5 18:24 snapshot.70000000c

After the ZooKeeper instance has been restored, run the following command to delete the backup file:

rm -rf /srv/BigData/zookeeper/version-2-bk

TingtingGG · Created Jun 29, 2019 10:14:41

Hey there!

Log in to the node where the original malfunctioning ZooKeeper instance resides and run the following command to check the directory.

ls -l /srv/BigData/zookeeper/version-2/.

If the directory is not blank, the instance has been restored.

Example:

-rw------- 1 omm wheel       1 Mar  5 18:24 acceptedEpoch
-rw------- 1 omm wheel       1 Mar  5 18:24 currentEpoch
-rw------- 1 omm wheel 67108880 Mar  5 18:31 log.600000001
-rw------- 1 omm wheel    873 Feb 27 02:47 snapshot.50000000d
-rw------- 1 omm wheel    665 Mar  5 18:13 snapshot.60000001d
-rw------- 1 omm wheel    849 Mar  5 18:24 snapshot.70000000c

After the ZooKeeper instance has been restored, run the following command to delete the backup file:

rm -rf /srv/BigData/zookeeper/version-2-bk

ZooKeeper instance is always in the Concerning state.

Best answer

Third Party’s Trade Secret

`@trans`bright_future`~trans`

My Followers

Enterprise

Consumer

Corporate

Carriers

ZooKeeper instance is always in the Concerning state.

Best answer

Third Party’s Trade Secret

`@trans`bright_future`~trans`

My Followers