前兩篇的博文已經完成了阿里伺服器的服務重啟，現在開始要把服務轉移到網易雲伺服器中。

1.網易的伺服器相比阿里的有些區別，要連線網易的伺服器需要經過一臺中轉的伺服器。

這時候連線伺服器稍微有些麻煩，需要一個隧道和代理。具體內容可以看下面的連結：

2.然後把第三方軟體安裝配置完成

包括：mysql，mongodb，kafka，redis，zookeeper，neo4j，java環境

先裝java環境 （centOS7.2  |  rpm方式   |   jdk-8u121-linux-x64）

首先解壓安裝

rpm -ivh jdk-8u121-linux-x64.rpm

解壓完成的jdk，會放在/usr/java/jdk1.8.0_121下面

什麼，vim都沒有？裝一下

yum -y install vim*

接著是配置環境變數

vim /etc/profile.d/java.sh

#java環境配置
JAVA_HOME=/usr/java/jdk1.8.0_121
JRE_HOME=${JAVA_HOME}/jre
CLASSPATH=.:${JAVA_HOME}/lib:${JRE_HOME}/lib
PATH=$PATH:$JAVA_HOME/bin:$JRE_HOME/bin
export JAVA_HOME JRE_HOME PATH CLASSPATH

然後讓source變數生效

source /etc/profile

之後，在終端使用echo命令檢查環境變數設定情況

[[email protected] ~]# echo $JAVA_HOME
/usr/java/jdk1.8.0_121

[[email protected] ~]# echo $CLASSPATH
.:/usr/java/jdk1.8.0_121/lib:/usr/java/jdk1.8.0_121/jre/lib

[[email protected] ~]# echo $PATH
/usr/java/jdk1.8.0_121/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/usr/java/jdk1.8.0_121/bin:/usr/java/jdk1.8.0_121/jre/bin:/usr/java/jdk1.8.0_121/bin:/usr/java/jdk1.8.0_121/jre/bin
 

最後檢查JDK是否安裝成功

[[email protected] ~]# java -version
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)

然後裝zookeeper總共有兩臺

解壓+改名（因為本就是root使用者下，所以不用加sudo）

tar -zxvf zookeeper-3.4.9.tar.gz -C /home/
mv /home/zookeeper-3.4.9 /home/zookeeper

配置zoo.cfg

[[email protected] zookeeper]# cd conf

[[email protected] conf]# cp zoo_sample.cfg zoo.cfg

[[email protected] conf]# vim zoo.cfg

先把dataDir=/tmp/zookeeper註釋，然後將下面四行程式碼新增到檔案末尾

dataDir=/home/data/zookeeper

server.1=192.168.16.86:2888:3888

server.2=192.168.16.84:2888:3888

儲存，然後建立目錄/home/data/zookeeper/data

建立myid檔案

[[email protected] conf]# cd /home/data/zookeeper/data

[[email protected] data]# touch myid

[[email protected] data]# echo "1">>myid

拷貝zookeeper
拷貝zookeeper到另外一臺機器

[[email protected] data]# scp -r /usr/local/zookeeper [email protected]:/usr/local/

中間會要求輸入密碼，分別輸入你另外兩臺機器的密碼就行了

修改myid檔案

192.168.1.92的myid內容改為2

[[email protected] zookeeper]# cd /usr/local/zookeeper/data

[[email protected] data]# echo "2">myid

開啟zookeeper埠

這裡要說一下，centOS7.2新開的伺服器，防火牆是鎖定的，所以要先解鎖防火牆，再啟動。

[[email protected] data]# systemctl unmask firewalld
Removed symlink /etc/systemd/system/firewalld.service.

然後再開啟防火牆，並檢查其狀態

[[email protected] data]# systemctl start firewalld
[[email protected] data]# systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2018-10-13 14:26:10 CST; 21s ago
     Docs: man:firewalld(1)
 Main PID: 12304 (firewalld)
   CGroup: /system.slice/firewalld.service
           └─12304 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

Oct 13 14:26:10 digdate-serv2.localdomain systemd[1]: Starting firewalld - dynamic firewall daemon...
Oct 13 14:26:10 digdate-serv2.localdomain systemd[1]: Started firewalld - dynamic firewall daemon.
Oct 13 14:26:10 digdate-serv2.localdomain firewalld[12304]: WARNING: ICMP type 'beyond-scope' is not supported by the ...pv6.
Oct 13 14:26:10 digdate-serv2.localdomain firewalld[12304]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP...ime.
Oct 13 14:26:10 digdate-serv2.localdomain firewalld[12304]: WARNING: ICMP type 'failed-policy' is not supported by the...pv6.
Oct 13 14:26:10 digdate-serv2.localdomain firewalld[12304]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICM...ime.
Oct 13 14:26:10 digdate-serv2.localdomain firewalld[12304]: WARNING: ICMP type 'reject-route' is not supported by the ...pv6.
Oct 13 14:26:10 digdate-serv2.localdomain firewalld[12304]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP...ime.
Hint: Some lines were ellipsized, use -l to show in full.

否則會報錯：Failed to start firewalld.service: Unit is masked.

開啟2888、3888、2181埠

[[email protected] data]# firewall-cmd --zone=public --add-port=2888/tcp --permanent

[[email protected] data]# firewall-cmd --zone=public --add-port=3888/tcp --permanent

[[email protected] data]# firewall-cmd --zone=public --add-port=2181/tcp --permanent

重啟防火牆

[[email protected] data]# firewall-cmd --reload

啟動zookeeper

1、啟動（每臺機器都要啟動）

[[email protected] bin]# /home/zookeeper/bin/zkServer.sh start

如果輸出以下內容，表示啟動成功

ZooKeeper JMX enabled by default
Using config: /usr/local/zookeeper/bin/../conf/zoo.cfg
Starting zookeeper ... STARTED 

2、  檢視狀態

[[email protected] data]# /usr/local/zookeeper/bin/zkServer.sh status

192.168.16.84

ZooKeeper JMX enabled by default
Using config: /home/zookeeper/bin/../conf/zoo.cfg
Mode: leader

192.168.16.86

ZooKeeper JMX enabled by default
Using config: /home/zookeeper/bin/../conf/zoo.cfg
Mode: follower

由此我們看出192.168.16.84這臺機器被自動選舉為leader了

這裡存在一個不穩定性，因為zookeeper最少需要三臺伺服器才能保證，一旦某一臺掛掉了，服務依然能夠正常執行，我這裡佈置的只有兩臺，所以一旦任意一臺掛掉，整個zookeeper就都掛掉了。

客戶端連線

[[email protected] ~]# /home/zookeeper/bin/zkCli.sh -timeout 5000 -server 192.168.16.86:2181

timeout：超過時間，單位毫秒

r：只讀模式，當結點換掉的時候，還可以提供讀服務

最終如下圖，表示連線成功：

Connecting to 192.168.16.86:2181
2018-10-13 15:33:58,933 [myid:] - INFO  [main:[email protected]] - Client environment:zookeeper.version=3.4.9-1757313, built on 08/23/2016 06:50 GMT
2018-10-13 15:33:58,937 [myid:] - INFO  [main:[email protected]] - Client environment:host.name=digdate-serv2.localdomain
2018-10-13 15:33:58,937 [myid:] - INFO  [main:[email protected]] - Client environment:java.version=1.8.0_121
2018-10-13 15:33:58,939 [myid:] - INFO  [main:[email protected]] - Client environment:java.vendor=Oracle Corporation
2018-10-13 15:33:58,939 [myid:] - INFO  [main:[email protected]] - Client environment:java.home=/usr/java/jdk1.8.0_121/jre
2018-10-13 15:33:58,939 [myid:] - INFO  [main:[email protected]] - Client environment:java.class.path=/home/zookeeper/bin/../build/classes:/home/zookeeper/bin/../build/lib/*.jar:/home/zookeeper/bin/../lib/slf4j-log4j12-1.6.1.jar:/home/zookeeper/bin/../lib/slf4j-api-1.6.1.jar:/home/zookeeper/bin/../lib/netty-3.10.5.Final.jar:/home/zookeeper/bin/../lib/log4j-1.2.16.jar:/home/zookeeper/bin/../lib/jline-0.9.94.jar:/home/zookeeper/bin/../zookeeper-3.4.9.jar:/home/zookeeper/bin/../src/java/lib/*.jar:/home/zookeeper/bin/../conf:.:/usr/java/jdk1.8.0_121/lib:/usr/java/jdk1.8.0_121/jre/lib
2018-10-13 15:33:58,940 [myid:] - INFO  [main:[email protected]] - Client environment:java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
2018-10-13 15:33:58,940 [myid:] - INFO  [main:[email protected]] - Client environment:java.io.tmpdir=/tmp
2018-10-13 15:33:58,940 [myid:] - INFO  [main:[email protected]] - Client environment:java.compiler=<NA>
2018-10-13 15:33:58,940 [myid:] - INFO  [main:[email protected]] - Client environment:os.name=Linux
2018-10-13 15:33:58,940 [myid:] - INFO  [main:[email protected]] - Client environment:os.arch=amd64
2018-10-13 15:33:58,940 [myid:] - INFO  [main:[email protected]] - Client environment:os.version=3.10.0-693.el7.x86_64
2018-10-13 15:33:58,940 [myid:] - INFO  [main:[email protected]] - Client environment:user.name=root
2018-10-13 15:33:58,940 [myid:] - INFO  [main:[email protected]] - Client environment:user.home=/root
2018-10-13 15:33:58,940 [myid:] - INFO  [main:[email protected]] - Client environment:user.dir=/root
2018-10-13 15:33:58,942 [myid:] - INFO  [main:[email protected]] - Initiating client connection, connectString=192.168.16.86 sessionTimeout=30000 [email protected]
Welcome to ZooKeeper!
2018-10-13 15:33:58,965 [myid:] - INFO  [main-SendThread(192.168.16.86:2181):[email protected]] - Opening socket connection to server 192.168.16.86/192.168.16.86:2181. Will not attempt to authenticate using SASL (unknown error)
JLine support is enabled
2018-10-13 15:33:59,036 [myid:] - INFO  [main-SendThread(192.168.16.86:2181):[email protected]] - Socket connection established to 192.168.16.86/192.168.16.86:2181, initiating session
[zk: 192.168.16.86(CONNECTING) 0] 2018-10-13 15:33:59,094 [myid:] - INFO  [main-SendThread(192.168.16.86:2181):[email protected]] - Session establishment complete on server 192.168.16.86/192.168.16.86:2181, sessionid = 0x1666c504f390000, negotiated timeout = 30000

WATCHER::

WatchedEvent state:SyncConnected type:None path:null

h：幫助列表

h
ZooKeeper -server host:port cmd args
    stat path [watch]
    set path data [version]
    ls path [watch]
    delquota [-n|-b] path
    ls2 path [watch]
    setAcl path acl
    setquota -n|-b val path
    history 
    redo cmdno
    printwatches on|off
    delete path [version]
    sync path
    listquota path
    rmr path
    get path [watch]
    create [-s] [-e] path data acl
    addauth scheme auth
    quit 
    getAcl path
    close 
    connect host:port

顯示能夠執行的命令

命令分類和資料庫相似，大概可以分為增刪改查四類

ZooKeeper資料結構：

大多數時候，我們隊ZooKeeper的操作都是在對節點進行增刪改查

常用命令：

查詢相關指令

ls path：列出path下的檔案

[zk: 127.0.0.1:2181(CONNECTED) 4] ls /
[zookeeper]

如上：列出根目錄節點下的所有檔案，目前就只有一個系統自帶的zookeeper節點

stat path：檢視節點狀態

[zk: 127.0.0.1:2181(CONNECTED) 6] stat /zookeeper
cZxid = 0x0
ctime = Thu Jan 01 08:00:00 CST 1970
mZxid = 0x0
mtime = Thu Jan 01 08:00:00 CST 1970
pZxid = 0x0
cversion = -1
dataVersion = 0
aclVersion = 0
ephemeralOwner = 0x0
dataLength = 0
numChildren = 1

cZxid:建立節點時的事務id

pZxid:子節點列表最後一次被修改的事務id
cversion:節點版本號
dataCersion:資料版本號
aclVerson:acl許可權版本號

......

get path：獲取指定節點的內容

ls2 path：列出path節點的子節點及狀態資訊


建立指令

create [-s] [-e] path data acl

1 [zk: 127.0.0.1:2181(CONNECTED) 10] create /node_1 123
2 Created /node_1

如上：在根目錄建立了node_1節點，攜帶資料 123

使用 get /node_1 驗證是否新增節點及其資料成功

[zk: 127.0.0.1:2181(CONNECTED) 15] create -e /node_1/node_1_1 234
Created /node_1/node_1_1

建立了一個臨時節點（-e），並且攜帶資料234，使用stat命令檢視這個新建的臨時節點

[zk: 127.0.0.1:2181(CONNECTED) 16] stat /node_1/node_1_1
cZxid = 0x200000003
ctime = Sat Aug 27 15:27:30 CST 2016
mZxid = 0x200000003
mtime = Sat Aug 27 15:27:30 CST 2016
pZxid = 0x200000003
cversion = 0
dataVersion = 0
aclVersion = 0
ephemeralOwner = 0x156cacb918b0000
dataLength = 3
numChildren = 0

ephemeralOwner值不再是0，表示這個臨時節點的版本號，如果是永久節點則其值為 0x0

1 [zk: 127.0.0.1:2181(CONNECTED) 1] create -s /node_1/node_1_1 234
2 Created /node_1/node_1_10000000001

通過使用-s引數，建立一個順序節點，我們雖然指定的節點名是node_1_1，但是實際上，名稱卻是 node_1_10000000001，如果我們重複執行：

[zk: 127.0.0.1:2181(CONNECTED) 2] create -s /node_1/node_1_1 234
Created /node_1/node_1_10000000002

效果如上

這個特性，我們可以利用一下，生成在分散式環境下的主鍵生成器。

-s 和 -e 可以同時使用

退出： quit

[zk: 127.0.0.1:2181(CONNECTED) 19] quit
Quitting...
2016-08-27 15:29:44,760 [myid:] - INFO  [main:[email protected]] - Session: 0x156cacb918b0000 closed
2016-08-27 15:29:44,763 [myid:] - INFO  [main-EventThread:[email protected]] - EventThread shut down for session: 0x156cacb918b0000

這個時候如果重新登入，執行 ls /node_1，發現其子節點是空的，建立的node_1_1子節點不見了，那是因為之前建立的時候就已經指定了，我們建立的是一個臨時節點。當客戶端會話結束後，臨時節點是會被刪除了。

修改相關指定：

set path data [version]

[zk: 127.0.0.1:2181(CONNECTED) 14] set /node_1 998
cZxid = 0x200000002
ctime = Sat Aug 27 15:24:39 CST 2016
mZxid = 0x20000000a
mtime = Sat Aug 27 15:38:40 CST 2016
pZxid = 0x200000008
cversion = 5
dataVersion = 2
aclVersion = 0
ephemeralOwner = 0x0
dataLength = 3
numChildren = 3

如果我們多次修改，會發現  dataVersion ，也就是資料版本，在不停得發生變化（自增）

如果我們在set的時候手動去指定了版本號，就必須和上一次查詢出來的結果一致，否則 就會報錯。

這個可以用於我們在修改節點資料的時候，保證我們修改前資料沒被別人修改過。因為如果別人修改過了，我們這次修改是不會成功的

刪除指令：

delete path [version]

刪除指定節點資料，其version引數的作用於set指定一致

delete /node_1/node_1_10000000001

整個節點全刪除

注意：delete只能刪除不包含子節點的節點，如果要刪除的節點包含子節點，使用rmr命令

rmr /node_1