Zookeeper笔记之使用zk实现集群选主
1、需求
在主从结构的集群中，咱们假设硬件机器是很脆弱的，随时可能会宕机，当master挂掉以后须要从slave中选出一个节点做为新的master，使用zookeeper能够很简单的实现集群选主功能。html
2、分析
下面为了方便叙述，将使用更通用的技术术语，即便用leader表示master，使用follower表示slave。java
集群选主涉及到两个问题：node
1. 谁来作leaderapache
2. leader挂掉了怎么被follower感知到网络
首先是第一个问题，谁来作leader，其实能够将这个问题看作是多线程中的互斥锁抢占，锁只有一把，而且只能被一我的抢到，这里就把一个zookeeper上的一个节点/leader-info看作是锁，集群中的每台机器都尝试去建立这个节点（抢占锁），由于zookeeper建立节点是原子性操做，因此只有一台机器可以建立成功其它都会失败，建立成功的那台机器就做为leader，其它机器作follower，通常leader抢占成功了以后会在/leader-info节点上存储一些与本身相关的信息，好比hostname、id之类的，以让follower知道谁抢占成功成为了leader，而后去链接leader进行一些数据交换或指令控制之类的，那就是选主以后的事了不在此篇文章的讨论范围以内。session
第二个问题是leader挂掉了怎么通知其它的follower，zookeeper中的节点按照有效时间分为持久节点和临时节点，临时节点跟session绑定，而一个session表示一个客户端，当客户端下线的时候session失效，当session失效的时候跟它绑定的临时节点就会被删除，利用这个特性能够检测节点是否还在存活状态，实现follower对leader下线的感知，只是须要注意在建立/leader-info节点的时候要将其建立为临时节点，而后众多follower都在这个节点上添加一个watcher监听其删除事件，这样当leader挂掉的时候session失效，而后与此session绑定的临时节点会被删除，即/leader-info节点将被删除，同时给全部的follower发送事件通知，follower一看leader挂了就燥起来了，将本身的状态置为looking，开始新一轮的选举。多线程
总结一下选主的流程：dom
1. 集群中的全部机器将本身置为looking状态，准备开始选举。分布式
2. 全部looking状态的机器尝试去建立/leader-info节点。优化
3. 建立成功的将本身的状态修改成leader，同时将本身的一些信息写入到/leader-info这个节点上。
4. 建立失败的将本身的状态置为follower，同时尝试从/leader-info获取leader信息进行一些leader改变的逻辑（在这里这个不是重点，打印一下便可），follower在获取/leader-info节点数据的同时要设置一个watcher，监听此节点的删除事件，当节点被删除事件触发时启动新一轮的选举，由于获取数据设置watcher这个操做是原子性的，因此要么这个节点存在获取数据成功，而且设置watcher也成功，要么节点不存在抛出KeeperException.NoNodeException异常。
5. 为何在follower设置watcher的时候还有可能会抛异常呢，leader不是已经建立了这个节点了吗？由于follower从尝试建立/leader-info节点失败到去获取此节点的数据同时设置watcher这一段操做不是原子性的，在这中间可能会发生一些变故，leader可能刚成为leader就挂掉了（或者由于一些网络抖动缘由，总之是session失效了），leader挂掉以后它建立的临时节点就被zookeeper删除了，因此当follower在设置watcher的时候若是检测到KeeperException.NoNodeException，说明以前的leader挂掉了，此时集群中已经没有了leader，follower又燥起来了，它将本身的状态置为looking开始新一轮的选举。
3、实现
Node.java：
package cc11001100.zookeeper.leaderElection;
import cc11001100.zookeeper.utils.ZooKeeperUtil;
import org.apache.zookeeper.CreateMode;
import org.apache.zookeeper.KeeperException;
import org.apache.zookeeper.Watcher;
import org.apache.zookeeper.ZooDefs;
import org.apache.zookeeper.ZooKeeper;
import java.io.IOException;
import java.io.UnsupportedEncodingException;
/**
* 表示集群中的一个节点
*
* @author CC11001100
*/
public class Node {
private Status status;
private String nodeForLeaderInfo;
private ZooKeeper zooKeeper;
public Node(String listenerNodeForLeader) throws IOException {
this.nodeForLeaderInfo = listenerNodeForLeader;
this.zooKeeper = ZooKeeperUtil.getZooKeeper();
lookingForLeader();
}
public void lookingForLeader() {
status = Status.LOOKING;
try {
String leaderInfo = Thread.currentThread().getName();
// 须要注意这里建立的是临时节点
zooKeeper.create(nodeForLeaderInfo, leaderInfo.getBytes(), ZooDefs.Ids.OPEN_ACL_UNSAFE, CreateMode.EPHEMERAL);
// 若是上一步没有抛异常，说明本身已是leader了
status = Status.LEADER;
String logMsg = Thread.currentThread().getName() + " is leader";
System.out.println(logMsg);
} catch (KeeperException.NodeExistsException e) {
// 节点已经存在，说明leader已经被别人注册成功了，本身是follower
status = Status.FOLLOWER;
try {
byte[] leaderInfoBytes = zooKeeper.getData(nodeForLeaderInfo, event -> {
if (event.getType() == Watcher.Event.EventType.NodeDeleted) {
lookingForLeader();
}
}, null);
String logMsg = Thread.currentThread().getName() + " is follower, master is " + new String(leaderInfoBytes, "UTF-8");
System.out.println(logMsg);
} catch (KeeperException.NoNodeException e1) {
// 若是在获取leader信息的时候报了节点不存在，说明这个leader比较短命，刚抢到leader就又挂掉了
lookingForLeader();
} catch (KeeperException | InterruptedException | UnsupportedEncodingException e1) {
e1.printStackTrace();
}
} catch (KeeperException | InterruptedException e) {
e.printStackTrace();
}
}
public void shutdown() {
try {
if (zooKeeper != null) {
zooKeeper.close();
}
} catch (InterruptedException e) {
e.printStackTrace();
}
}
public Status getStatus() {
return status;
}
// 当前节点的状态，节点的状态必须在这三个中的一个
public enum Status {
LOOKING, // 选举中
LEADER, // 选举完毕，当前节点为leader
FOLLOWER; // 选举完毕，当前节点为follower
}
}
LeaderElectionTest.java：
package cc11001100.zookeeper.leaderElection;
import java.io.IOException;
import java.util.concurrent.TimeUnit;
import java.util.concurrent.atomic.AtomicInteger;
import java.util.concurrent.atomic.AtomicLong;
/**
* @author CC11001100
*/
public class LeaderElectionTest {
private static void sleep(long mils) {
try {
TimeUnit.MILLISECONDS.sleep(mils);
} catch (InterruptedException e) {
e.printStackTrace();
}
}
public static void main(String[] args) throws IOException {
final String LEADER_INFO_NODE = "/leader-info";
int nodeNum = 10;
AtomicLong idGenerator = new AtomicLong();
AtomicInteger activeNodeCount = new AtomicInteger();
while (true) {
if (activeNodeCount.get() >= nodeNum) {
sleep(10);
continue;
}
// 线程启动须要必定时间，将线程启动看作开机过程，在开机以前就算一台新的机器加入了
activeNodeCount.incrementAndGet();
new Thread(() -> {
try {
Node node = new Node(LEADER_INFO_NODE);
while (true) {
sleep(1000);
// 这里为了试验就让leader有轻微自杀倾向...
if (node.getStatus() == Node.Status.LEADER && Math.random() < 0.3) {
String logMsg = "----------------------------- " + Thread.currentThread().getName() + " shutdown -----------------------------";
System.out.println(logMsg);
node.shutdown();
break;
}
}
} catch (IOException e) {
e.printStackTrace();
} finally {
activeNodeCount.decrementAndGet();
}
}, "node-" + idGenerator.getAndIncrement()).start();
}
}
}
控制台输出：
... node-4 is leader node-3 is follower, master is node-4 node-0 is follower, master is node-4 node-9 is follower, master is node-4 node-7 is follower, master is node-4 node-5 is follower, master is node-4 node-1 is follower, master is node-4 node-6 is follower, master is node-4 node-8 is follower, master is node-4 node-2 is follower, master is node-4 ----------------------------- node-4 shutdown ----------------------------- node-0-EventThread is leader node-6-EventThread is follower, master is node-0-EventThread node-3-EventThread is follower, master is node-0-EventThread node-7-EventThread is follower, master is node-0-EventThread node-1-EventThread is follower, master is node-0-EventThread node-5-EventThread is follower, master is node-0-EventThread node-9-EventThread is follower, master is node-0-EventThread node-2-EventThread is follower, master is node-0-EventThread node-8-EventThread is follower, master is node-0-EventThread node-10 is follower, master is node-0-EventThread ----------------------------- node-0 shutdown ----------------------------- node-6-EventThread is leader node-7-EventThread is follower, master is node-6-EventThread node-1-EventThread is follower, master is node-6-EventThread node-3-EventThread is follower, master is node-6-EventThread node-10-EventThread is follower, master is node-6-EventThread node-9-EventThread is follower, master is node-6-EventThread node-5-EventThread is follower, master is node-6-EventThread node-2-EventThread is follower, master is node-6-EventThread node-8-EventThread is follower, master is node-6-EventThread node-11 is follower, master is node-6-EventThread ----------------------------- node-6 shutdown ----------------------------- node-1-EventThread is leader node-10-EventThread is follower, master is node-1-EventThread node-7-EventThread is follower, master is node-1-EventThread node-11-EventThread is follower, master is node-1-EventThread node-8-EventThread is follower, master is node-1-EventThread node-5-EventThread is follower, master is node-1-EventThread node-9-EventThread is follower, master is node-1-EventThread node-3-EventThread is follower, master is node-1-EventThread node-2-EventThread is follower, master is node-1-EventThread node-12 is follower, master is node-1-EventThread ----------------------------- node-1 shutdown ----------------------------- node-3-EventThread is leader node-12-EventThread is follower, master is node-3-EventThread node-11-EventThread is follower, master is node-3-EventThread node-5-EventThread is follower, master is node-3-EventThread node-7-EventThread is follower, master is node-3-EventThread node-9-EventThread is follower, master is node-3-EventThread node-2-EventThread is follower, master is node-3-EventThread node-10-EventThread is follower, master is node-3-EventThread node-8-EventThread is follower, master is node-3-EventThread node-13 is follower, master is node-3-EventThread ----------------------------- node-3 shutdown ----------------------------- node-5-EventThread is leader node-13-EventThread is follower, master is node-5-EventThread node-12-EventThread is follower, master is node-5-EventThread node-7-EventThread is follower, master is node-5-EventThread node-11-EventThread is follower, master is node-5-EventThread node-10-EventThread is follower, master is node-5-EventThread node-9-EventThread is follower, master is node-5-EventThread node-2-EventThread is follower, master is node-5-EventThread node-8-EventThread is follower, master is node-5-EventThread node-14 is follower, master is node-5-EventThread ----------------------------- node-5 shutdown ----------------------------- node-7-EventThread is leader node-13-EventThread is follower, master is node-7-EventThread node-12-EventThread is follower, master is node-7-EventThread node-9-EventThread is follower, master is node-7-EventThread node-11-EventThread is follower, master is node-7-EventThread node-14-EventThread is follower, master is node-7-EventThread node-10-EventThread is follower, master is node-7-EventThread node-8-EventThread is follower, master is node-7-EventThread node-2-EventThread is follower, master is node-7-EventThread node-15 is follower, master is node-7-EventThread ----------------------------- node-7 shutdown ----------------------------- node-14-EventThread is leader node-13-EventThread is follower, master is node-14-EventThread node-11-EventThread is follower, master is node-14-EventThread node-2-EventThread is follower, master is node-14-EventThread node-12-EventThread is follower, master is node-14-EventThread node-15-EventThread is follower, master is node-14-EventThread node-10-EventThread is follower, master is node-14-EventThread node-9-EventThread is follower, master is node-14-EventThread node-8-EventThread is follower, master is node-14-EventThread node-16 is follower, master is node-14-EventThread ----------------------------- node-14 shutdown ----------------------------- node-13-EventThread is leader node-12-EventThread is follower, master is node-13-EventThread node-15-EventThread is follower, master is node-13-EventThread node-9-EventThread is follower, master is node-13-EventThread node-10-EventThread is follower, master is node-13-EventThread node-2-EventThread is follower, master is node-13-EventThread node-8-EventThread is follower, master is node-13-EventThread node-11-EventThread is follower, master is node-13-EventThread node-16-EventThread is follower, master is node-13-EventThread node-17 is follower, master is node-13-EventThread ...
最后有个须要注意的地方就是是否须要将leader节点设置为顺序临时节点呢？相似于分布式锁那样，这样的话每次唤醒一个节点就能够了，这看上去像是一个能够优化的点。
其实并非，当leader挂掉的时候必须全部follower都可以感知到leader的变动，即便他们不参与抢主也必须醒来执行leader变动的逻辑。
.
相关文章
- 1. Zookeeper(4)---ZK集群部署和选举
- 2. 使用zk实现主从选举
- 3. zookeeper笔记之基于zk实现分布式锁
- 4. zookeeper（三）zk集群应该怎么实现
- 5. kafka+zk 集群--3个broker 3个zookeeper
- 6. ZooKeeper----ZooKeeper 集群使用
- 7. zookeeper集群选举
- 8. 使用Zookeeper实现选举
- 9. zookeeper实现主从选举
- 10. 【sentinel】sentinel实现zookeeper集群
- 更多相关文章...
- • Swarm 集群管理 - Docker教程
- • ADO Recordset（记录集） - ADO 教程
- • Tomcat学习笔记（史上最全tomcat学习笔记）
- • ☆基于Java Instrument的Agent实现
相关标签/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
最新文章
- 1. vs2019运行opencv图片显示代码时，窗口乱码
- 2. app自动化 - 元素定位不到？别慌，看完你就能解决
- 3. 在Win8下用cisco ××× Client连接时报Reason 422错误的解决方法
- 4. eclipse快速补全代码
- 5. Eclipse中Java/Html/Css/Jsp/JavaScript等代码的格式化
- 6. idea+spring boot +mabitys(wanglezapin)+mysql (1)
- 7. 勒索病毒发生变种 新文件名将带有“.UIWIX”后缀
- 8. 【原创】Python 源文件编码解读
- 9. iOS9企业部署分发问题深入了解与解决
- 10. 安装pytorch报错CondaHTTPError：******
欢迎关注本站公众号,获取更多信息
