随笔 - 241  文章 - 1  评论 - 58  阅读 - 85万 

前言

在分布式集群架构中各个组件之间如何解决以下2个关键问题?

1.配置共享:共享同一份配置文件,如果这份配置文件更新之后,各个组件如何马上得知(我就是冲着watch for changes来的....)?

2.服务注册发现:集群中新增节点如何做到自动发现?

 

etcd简介

 

etcd是Go语言开发的一个开源的、支持分布式的、高可用的key-value存储系统。

可用于组册发现、配置共享中心。

A distributed, reliable key-value store for the most critical data of a distributed system.

是什么优势让etcd官网说 for the most critical data?

优势:

完全复制:etcd集群中的每个节点都可以使用完整的文档

高可用:防止单点故障有leader和follower的选举机制

一致性:每次读取都会返回跨多主机的最新写入

部署简单:二进制直接运行

安全:支持TSL

数据可靠:使用Raft算法实现各etcd间存储的数据强一致性。

 ps:etcd使用raft算法实现了分布式锁。保证了etcd集群中节点中存储的数据永远一致,

也就是说1个Python程序和1个Go程序同时向etcd中put同1个key是有锁的。

 

架构

 

 

从etcd的架构图中可以看到,etcd主要分为4个部分。

http server:用户client发送的API操作请求、以及其他etcd节点的同步和心跳新校区

store:处理etcd支持的各类功能事物,包括索引、节点变更、监控反馈、事件处理和执行,是API请求的具体实现。

Raft:etcd集群中数据一致性的关键

Wal(write ahead log):预写日志,是etcd数据存储的方式,实现持久化存储。

 

使用etcd

2379端口:接收client的http请求

2380端口:用于etcd集群节点间通信

 

启动

复制代码
root@zhanggen etcd-v3.3.18-linux-amd64]# ./etcd --name master1 --data-dir /data/etcd/ --wal-dir /data/etcd/wal/ --listen-client-urls http://0.0.0.0:2371 --advertise-client-urls http://0.0.0.0:2371 --listen-peer-urls http://0.0.0.0:2381
2020-05-21 01:35:01.096751 I | etcdmain: etcd Version: 3.3.18
2020-05-21 01:35:01.096801 I | etcdmain: Git SHA: 3c8740a79
2020-05-21 01:35:01.096806 I | etcdmain: Go Version: go1.12.9
2020-05-21 01:35:01.096809 I | etcdmain: Go OS/Arch: linux/amd64
2020-05-21 01:35:01.096812 I | etcdmain: setting maximum number of CPUs to 1, total number of available CPUs is 1
2020-05-21 01:35:01.096820 I | etcdmain: advertising using detected default host "192.168.56.133"
2020-05-21 01:35:01.096852 N | etcdmain: the server is already initialized as member before, starting as etcd member...
2020-05-21 01:35:01.097083 I | embed: listening for peers on http://0.0.0.0:2381
2020-05-21 01:35:01.097118 I | embed: listening for client requests on 0.0.0.0:2371
2020-05-21 01:35:01.102854 I | etcdserver: name = master1
2020-05-21 01:35:01.102869 I | etcdserver: data dir = /data/etcd/
2020-05-21 01:35:01.102877 I | etcdserver: member dir = /data/etcd/member
2020-05-21 01:35:01.102879 I | etcdserver: dedicated WAL dir = /data/etcd/wal/
2020-05-21 01:35:01.102882 I | etcdserver: heartbeat = 100ms
2020-05-21 01:35:01.102885 I | etcdserver: election = 1000ms
2020-05-21 01:35:01.102887 I | etcdserver: snapshot count = 100000
2020-05-21 01:35:01.102895 I | etcdserver: advertise client URLs = http://0.0.0.0:2371
2020-05-21 01:35:01.102899 I | etcdserver: initial advertise peer URLs = http://192.168.56.133:2381
2020-05-21 01:35:01.102905 I | etcdserver: initial cluster = master1=http://192.168.56.133:2381
2020-05-21 01:35:01.112656 I | etcdserver: starting member 36d9af938bdf88c5 in cluster 24d7db2fa7e0796c
2020-05-21 01:35:01.112685 I | raft: 36d9af938bdf88c5 became follower at term 0
2020-05-21 01:35:01.112696 I | raft: newRaft 36d9af938bdf88c5 [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
2020-05-21 01:35:01.112699 I | raft: 36d9af938bdf88c5 became follower at term 1
2020-05-21 01:35:01.115541 W | auth: simple token is not cryptographically signed
2020-05-21 01:35:01.117263 I | etcdserver: starting server... [version: 3.3.18, cluster version: to_be_decided]
2020-05-21 01:35:01.119207 I | etcdserver: 36d9af938bdf88c5 as single-node; fast-forwarding 9 ticks (election ticks 10)
2020-05-21 01:35:01.119674 I | etcdserver/membership: added member 36d9af938bdf88c5 [http://192.168.56.133:2381] to cluster 24d7db2fa7e0796c
2020-05-21 01:35:01.413844 I | raft: 36d9af938bdf88c5 is starting a new election at term 1
2020-05-21 01:35:01.413947 I | raft: 36d9af938bdf88c5 became candidate at term 2
2020-05-21 01:35:01.414120 I | raft: 36d9af938bdf88c5 received MsgVoteResp from 36d9af938bdf88c5 at term 2
2020-05-21 01:35:01.414179 I | raft: 36d9af938bdf88c5 became leader at term 2
2020-05-21 01:35:01.414206 I | raft: raft.node: 36d9af938bdf88c5 elected leader 36d9af938bdf88c5 at term 2
2020-05-21 01:35:01.415431 I | etcdserver: setting up the initial cluster version to 3.3
2020-05-21 01:35:01.420094 N | etcdserver/membership: set the initial cluster version to 3.3
2020-05-21 01:35:01.420297 I | etcdserver/api: enabled capabilities for version 3.3
2020-05-21 01:35:01.420398 I | etcdserver: published {Name:master1 ClientURLs:[http://0.0.0.0:2371]} to cluster 24d7db2fa7e0796c
2020-05-21 01:35:01.421353 E | etcdmain: forgot to set Type=notify in systemd service file?
2020-05-21 01:35:01.421407 I | embed: ready to serve client requests
2020-05-21 01:35:01.424229 N | embed: serving insecure client requests on [::]:2371, this is strongly discouraged!
复制代码

 

测试

[root@zhanggen etcd-v3.3.18-linux-amd64]# export ETCDCTL_API=3
[root@zhanggen etcd-v3.3.18-linux-amd64]# ./etcdctl --endpoints=192.168.56.133:2371 put name "Martin"
OK
[root@zhanggen etcd-v3.3.18-linux-amd64]# ./etcdctl --endpoints=192.168.56.133:2371 get name 
name
Martiin
[root@zhanggen etcd-v3.3.18-linux-amd64]# 

 

go连接etcd

D:\goproject\src\jd.com\etcdDemo>go get go.etcd.io/etcd/clientv3
go: downloading google.golang.org/grpc v1.26.0
go: downloading github.com/golang/protobuf v1.3.2
go: extracting github.com/golang/protobuf v1.3.2
go: extracting google.golang.org/grpc v1.26.0

 

 put和get模式

  

watch模式

排1个哨兵去监控key发生的事件,马上通知给我!(watcher模式可以实现配置文件的热加载!)

  

利用etcd的watcher功能实现配置信息热加载

  

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

参考

posted on   Martin8866  阅读(1623)  评论(0编辑  收藏  举报
编辑推荐:
· SQL Server 2025 AI相关能力初探
· Linux系列:如何用 C#调用 C方法造成内存泄露
· AI与.NET技术实操系列(二):开始使用ML.NET
· 记一次.NET内存居高不下排查解决与启示
· 探究高空视频全景AR技术的实现原理
阅读排行:
· 阿里最新开源QwQ-32B,效果媲美deepseek-r1满血版,部署成本又又又降低了!
· SQL Server 2025 AI相关能力初探
· AI编程工具终极对决:字节Trae VS Cursor,谁才是开发者新宠?
· 开源Multi-agent AI智能体框架aevatar.ai,欢迎大家贡献代码
· Manus重磅发布:全球首款通用AI代理技术深度解析与实战指南
历史上的今天:
2017-05-21 抽屉首页
点击右上角即可分享
微信分享提示