k8s上搭建zookeeper集群和kafka集群

最新推荐文章于 2024-04-20 20:42:55 发布
最新推荐文章于 2024-04-20 20:42:55 发布
阅读量2.9k 收藏 5
点赞数
文章标签： kubernetes
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/gy13477001651/article/details/106502548
版权

k8s上搭建zookeeper集群和kafka集群

一.zookeeper集群搭建

1.原计划是在一个development下创建三个副本，后来发现不行，如果是一个development，那么三个副本的yml是一模一样的，而zookeeper集群中每个节点的myid不能一样，故需要创建三份development
2.集群节点之间需要通信，就需要建立service，但是不能经service的负载均衡，需要直达pod，有两种法方法可以实现

  • 1）service建成headless
    service，这样就可以通过pod的名字直接找到pod，配置server.1=zookeeper1:2888:3888;2181即可到达pod，其中zookeeper1是service名称

  • 2）service建成普通service，使用server.1=zookeeper1-0.zookeeper1.kafka.svc.cluster.local:2888:3888;2181，可以到达pod

3.为了简单起见，没有使用nfs，如果需要自行加上挂载
4.顺便列出下zookeeper的作用，方便自己记忆

  1. 数据发布与订阅（配置中心）
  2. 负载均衡
  3. 命名服务(Naming Service)
  4. 分布式通知/协调
  5. 集群管理与Master选举
  6. 分布式锁
  7. 分布式队列

前提：创建namespace kafka,我们构建的内容都放到这里面

1.node1


---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  annotations:
    k8s.eip.work/ingress: 'false'
    k8s.eip.work/service: None
    k8s.eip.work/workload: zookeeper1
  labels:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: zookeeper1
  name: zookeeper1
  namespace: kafka
spec:
  podManagementPolicy: OrderedReady
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s.eip.work/layer: cloud
      k8s.eip.work/name: zookeeper1
  serviceName: zookeeper1
  template:
    metadata:
      labels:
        k8s.eip.work/layer: cloud
        k8s.eip.work/name: zookeeper1
    spec:
      containers:
        - env:
          - name: ZOO_SERVERS
            value: >-
              #下面两种方法都可以，一种直接到pod，一种到headless servcie（下面只有一个pod）
              #server.1=zookeeper1-0.zookeeper1.kafka.svc.cluster.local:2888:3888;2181
              #server.2=zookeeper2-0.zookeeper2.kafka.svc.cluster.local:2888:3888;2181
              #server.3=zookeeper3-0.zookeeper3.kafka.svc.cluster.local:2888:3888;2181
              server.1=zookeeper1:2888:3888;2181
              server.2=zookeeper2:2888:3888;2181
              server.3=zookeeper3:2888:3888;2181
          - name: ZOO_MY_ID
            value: '1'
          image: zookeeper
          imagePullPolicy: IfNotPresent
          name: zookeeper
          ports:
            - containerPort: 2181
              name: client
              protocol: TCP
            - containerPort: 2888
              name: server
              protocol: TCP
            - containerPort: 3888
              name: leader-election
              protocol: TCP

---
apiVersion: v1
kind: Service
metadata:
  annotations:
    k8s.eip.work/workload: zookeeper1
  labels:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: zookeeper1
  name: zookeeper1
  namespace: kafka
spec:
  clusterIP: None
  selector:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: zookeeper1
  type: ClusterIP

2.node2


---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  annotations:
    k8s.eip.work/ingress: 'false'
    k8s.eip.work/service: None
    k8s.eip.work/workload: zookeeper2
  labels:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: zookeeper2
  name: zookeeper2
  namespace: kafka
spec:
  podManagementPolicy: OrderedReady
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s.eip.work/layer: cloud
      k8s.eip.work/name: zookeeper2
  serviceName: zookeeper2
  template:
    metadata:
      labels:
        k8s.eip.work/layer: cloud
        k8s.eip.work/name: zookeeper2
    spec:
      containers:
        - env:
          - name: ZOO_SERVERS
            value: >-
              #下面两种方法都可以，一种直接到pod，一种到headless servcie（下面只有一个pod）
              #server.1=zookeeper1-0.zookeeper1.kafka.svc.cluster.local:2888:3888;2181
              #server.2=zookeeper2-0.zookeeper2.kafka.svc.cluster.local:2888:3888;2181
              #server.3=zookeeper3-0.zookeeper3.kafka.svc.cluster.local:2888:3888;2181
              server.1=zookeeper1:2888:3888;2181
              server.2=zookeeper2:2888:3888;2181
              server.3=zookeeper3:2888:3888;2181
          - name: ZOO_MY_ID
            value: '2'
          image: zookeeper
          imagePullPolicy: IfNotPresent
          name: zookeeper
          ports:
            - containerPort: 2181
              name: client
              protocol: TCP
            - containerPort: 2888
              name: server
              protocol: TCP
            - containerPort: 3888
              name: leader-election
              protocol: TCP

---
apiVersion: v1
kind: Service
metadata:
  annotations:
    k8s.eip.work/workload: zookeeper2
  labels:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: zookeeper2
  name: zookeeper2
  namespace: kafka
spec:
  clusterIP: None
  selector:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: zookeeper2
  type: ClusterIP

3.node3

---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  annotations:
    k8s.eip.work/ingress: 'false'
    k8s.eip.work/service: None
    k8s.eip.work/workload: zookeeper3
  labels:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: zookeeper3
  name: zookeeper3
  namespace: kafka
spec:
  podManagementPolicy: OrderedReady
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s.eip.work/layer: cloud
      k8s.eip.work/name: zookeeper3
  serviceName: zookeeper3
  template:
    metadata:
      labels:
        k8s.eip.work/layer: cloud
        k8s.eip.work/name: zookeeper3
    spec:
      containers:
        - env:
          - name: ZOO_SERVERS
            value: >-
              #下面两种方法都可以，一种直接到pod，一种到headless servcie（下面只有一个pod）
              #server.1=zookeeper1-0.zookeeper1.kafka.svc.cluster.local:2888:3888;2181
              #server.2=zookeeper2-0.zookeeper2.kafka.svc.cluster.local:2888:3888;2181
              #server.3=zookeeper3-0.zookeeper3.kafka.svc.cluster.local:2888:3888;2181
              server.1=zookeeper1:2888:3888;2181
              server.2=zookeeper2:2888:3888;2181
              server.3=zookeeper3:2888:3888;2181
          - name: ZOO_MY_ID
            value: '3'
          image: zookeeper
          imagePullPolicy: IfNotPresent
          name: zookeeper
          ports:
            - containerPort: 2181
              name: client
              protocol: TCP
            - containerPort: 2888
              name: server
              protocol: TCP
            - containerPort: 3888
              name: leader-election
              protocol: TCP
---
apiVersion: v1
kind: Service
metadata:
  annotations:
    k8s.eip.work/workload: zookeeper3
  labels:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: zookeeper3
  name: zookeeper3
  namespace: kafka
spec:
  clusterIP: None
  selector:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: zookeeper3
  type: ClusterIP

4.验证是否成功

Mode: follower或leader说明集群部署成功

root@zookeeper1-0:/apache-zookeeper-3.6.1-bin# zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /conf/zoo.cfg
Client port found: 2181. Client address: localhost.
Mode: follower

二.kafka集群搭建

1.broker.id一定要指定，否则每次启动会自动生成，很有问题，有可能找不到分区leader
2.注意：name=kafka会有如下问题，但是可以通过增加环境变量KAFKA_PORT来解决，或者不要叫kafka

rg.apache.kafka.common.config.ConfigException: Invalid value tcp://10.0.35.234:9092 for configuration port: Not a number of type INT

1.node1

---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  annotations:
    k8s.eip.work/ingress: 'false'
    k8s.eip.work/service: NodePort
    k8s.eip.work/workload: kafka1
  labels:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: kafka1
  name: kafka1
  namespace: kafka
spec:
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s.eip.work/layer: cloud
      k8s.eip.work/name: kafka1
  serviceName: kafka1
  template:
    metadata:
      labels:
        k8s.eip.work/layer: cloud
        k8s.eip.work/name: kafka1
    spec:
      containers:
        - env:
            - name: KAFKA_ZOOKEEPER_CONNECT
              value: 'zookeeper1:2181,zookeeper2:2181,zookeeper3:2181'
            - name: KAFKA_LISTENERS
              value: 'PLAINTEXT://:9092'
            - name: KAFKA_ADVERTISED_LISTENERS
              value: 'PLAINTEXT://192.168.100.16:31367'
            - name: KAFKA_BROKER_ID
              value: '1'
          image: wurstmeister/kafka
          imagePullPolicy: IfNotPresent
          name: kafka
          ports:
            - containerPort: 9092
              protocol: TCP
            - containerPort: 1099
              protocol: TCP
---
apiVersion: v1
kind: Service
metadata:
  annotations:
    k8s.eip.work/workload: kafka1
  labels:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: kafka1
  name: kafka1
  namespace: kafka
spec:
  ports:
    - name: zhnz8q
      nodePort: 31367
      port: 9092
      protocol: TCP
      targetPort: 9092
  selector:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: kafka1
  sessionAffinity: None
  type: NodePort

2.node2

---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  annotations:
    k8s.eip.work/ingress: 'false'
    k8s.eip.work/service: NodePort
    k8s.eip.work/workload: kafka2
  labels:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: kafka2
  name: kafka2
  namespace: kafka
spec:
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s.eip.work/layer: cloud
      k8s.eip.work/name: kafka2
  serviceName: kafka2
  template:
    metadata:
      labels:
        k8s.eip.work/layer: cloud
        k8s.eip.work/name: kafka2
    spec:
      containers:
        - env:
            - name: KAFKA_ZOOKEEPER_CONNECT
              value: 'zookeeper1:2181,zookeeper2:2181,zookeeper3:2181'
            - name: KAFKA_LISTENERS
              value: 'PLAINTEXT://:9092'
            - name: KAFKA_ADVERTISED_LISTENERS
              value: 'PLAINTEXT://192.168.100.16:31368'
            - name: KAFKA_BROKER_ID
              value: '2'
          image: wurstmeister/kafka
          imagePullPolicy: IfNotPresent
          name: kafka
          ports:
            - containerPort: 9092
              protocol: TCP
            - containerPort: 1099
              protocol: TCP
---
apiVersion: v1
kind: Service
metadata:
  annotations:
    k8s.eip.work/workload: kafka2
  labels:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: kafka2
  name: kafka2
  namespace: kafka
spec:
  ports:
    - nodePort: 31368
      port: 9092
      protocol: TCP
      targetPort: 9092
  selector:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: kafka2
  sessionAffinity: None
  type: NodePort

3.node3

---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  annotations:
    k8s.eip.work/ingress: 'false'
    k8s.eip.work/service: NodePort
    k8s.eip.work/workload: kafka3
  labels:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: kafka3
  name: kafka3
  namespace: kafka
spec:
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s.eip.work/layer: cloud
      k8s.eip.work/name: kafka3
  serviceName: kafka3
  template:
    metadata:
      labels:
        k8s.eip.work/layer: cloud
        k8s.eip.work/name: kafka3
    spec:
      containers:
        - env:
            - name: KAFKA_ZOOKEEPER_CONNECT
              value: 'zookeeper1:2181,zookeeper2:2181,zookeeper3:2181'
            - name: KAFKA_LISTENERS
              value: 'PLAINTEXT://:9092'
            - name: KAFKA_ADVERTISED_LISTENERS
              value: 'PLAINTEXT://192.168.100.16:31369'
            - name: KAFKA_BROKER_ID
              value: '3'
          image: wurstmeister/kafka
          imagePullPolicy: IfNotPresent
          name: kafka
          ports:
            - containerPort: 9092
              protocol: TCP
            - containerPort: 1099
              protocol: TCP
---
apiVersion: v1
kind: Service
metadata:
  annotations:
    k8s.eip.work/workload: kafka3
  labels:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: kafka2
  name: kafka3
  namespace: kafka
spec:
  ports:
    - nodePort: 31369
      port: 9092
      protocol: TCP
      targetPort: 9092
  selector:
    k8s.eip.work/layer: cloud
    k8s.eip.work/name: kafka3
  sessionAffinity: None
  type: NodePort

2.问题解决

1.如果kafka已经连接上zoo，zoo重启后，日志中会不停的打印，同时kafka日志也会不停的打印信息，说连不上，不是已经配置了多个吗，好像不起作用？

2020-06-02 11:29:07,541 [myid:1] - INFO  [NIOWorkerThread-2:ZooKeeperServer@1375] - Refusing session request for client /10.100.15.190:52678 as it has seen zxid 0x10000002e our last zxid is 0x0 client must try another server
2020-06-02 11:29:09,925 [myid:1] - INFO  [NIOWorkerThread-1:ZooKeeperServer@1375] - Refusing session request for client /10.100.5.193:42016 as it has seen zxid 0x10000003f our last zxid is 0x0 client must try another server

2.客户端连接报如下异常，如果topic是新的则报，什么鬼？

bash-4.4# kafka-console-producer.sh --broker-list kafka1:9092 --topic zipkin>
[2020-06-02 12:09:34,009] WARN [Producer clientId=console-producer] 1 partitions have leader brokers without a matching listener, including [zipkin-0] (org.apache.kafka.clients.NetworkClient)
>[2020-06-02 12:09:34,108] WARN [Producer clientId=console-producer] 1 partitions have leader brokers without a matching listener, including [zipkin-0] (org.apache.kafka.clients.NetworkClient)

原因：kafka的boker.id要指定，如果变化，则找不到分区leader就报这个错误

得之
关注
  • 0
    点赞
  • 踩
  • 5
    收藏
    觉得还不错? 一键收藏
  • 2
    评论
k8s部署zookeeper+kafka集群
dhshttgb的博客
04-13 915
一、相关版本信息 k8s v1.17.16 kafka registry.hub.docker.com/leey18/k8skafka:v1 zookeeper registry.hub.docker.com/linzhaoming/k8szk:v2 我们是部署集群3台kafka，3台zookeeper。 二、Persistent Volume存储的创建 1.创建pv （1）分别登录3台worker服务器，创建yaml中对应的文件夹路径，对应创建多个PV，zookeeper服务和kafka服务各3个,一共创
Kubernetes搭建Zookeeper和Kafka集群
Daniel462038751的专栏
11-12 1291
Kafka 提示：这里可以添加系列文章的所有文章的目录，目录需要自己手动添加 例如：第一章 Python 机器学习入门之pandas的使用 提示：写完文章后，目录可以自动生成，如何生成可参考右边的帮助文档 文章目录 系列文章目录 前言 一、pandas是什么？ 二、使用步骤 1.引入库 2.读入数据 总结 前言 Kubernetes搭建Zookeeper和Kafka集群 一、搭建Zookeeper集群 1.创建集群Service的zookeeper-svc.ya
K8s 部署 Zookeeper 和 Kafka 集群
最新发布
小毕超博客
04-20 532
K8s 部署 Zookeeper 和 Kafka 集群
k8s集群安装部署kafka、zookeeper集群
weixin_40668374的博客
09-18 2780
k8s集群安装部署kafka、zookeeper集群 注： 有状态、可持续换集成 redis集群有两种部署方式 StatefulSet Service&Deployment 一、创建NFS存储 找一个k8s节点安装（我是在master节点安装） 创建NFS存储 创建NFS存储主要是为了给kafka、zookeeper提供稳定的后端存储，当kafka、zookeeper的Pod发生故障重启或迁移后，依然能获得原先的数据。 这里，我们先要创建NFS，然后通过使用PV为kafka、zookeeper挂载
k8s部署zookeeper集群
Yuan_xii的博客
12-30 1413
apiVersion: v1 kind: Service metadata: name: zk-hs labels: app: zk spec: selector: app: zk ports: - port: 2888 name: server - port: 3888 name: leader-election culsterIP: None --- apiVersion: v1 kind: Service metadata: name:
K8S 部署Zookeeper集群
weixin_44602192的博客
11-12 2166
1.创建PV pv.yaml文件内容如下： --- apiVersion: v1 kind: PersistentVolume metadata: name: zkpv01 spec: accessModes: - ReadWriteMany storageClassName: nfs capacity: storage: 5Gi persistentVolumeReclaimPolicy: Retain nfs: path: /data/nfsDir/zook
Docker搭建Zookeeper&Kafka集群的实现
09-29
主要介绍了Docker搭建Zookeeper&Kafka集群的实现，文中通过示例代码介绍的非常详细，对大家的学习或者工作具有一定的参考学习价值，需要的朋友们下面随着小编来一起学习学习吧
基于k8s的zookeeper集群
08-20
基于k8s的zookeeper集群，已做好亲和力和反亲和。并使用了hostpath的方式。也可以自行改为pv-pvc
kafka + zookeeper 集群jar包
02-11
kafka_2.12-2.2.1.tgz zookeeper-3.4.14.tar.gz
Zookeeper集群搭建.doc
12-15
需要三台机器安装zookeeper集群：安装JDK环境、安装部署zookeeper集群、启动zookeeper集群、修改配置
4-6 k8s构建zookeeper集群
分享云原生，容器，运维等干货知识
08-28 1173
ZooKeeper是一个分布式的，开放源码的分布式应用程序协调服务，是Google的Chubby一个开源的实现，是Hadoop和Hbase的重要组件。它是一个为分布式应用提供一致性服务的软件，提供的功能包括：配置维护、域名服务、分布式同步、组服务等。下面我们通过k8s构建zookeeper镜像，上传私有仓库，创建PV/PVC，最后yaml部署3个节点的zookeeper集群。集群需要奇数位，本文创建了3个pv，3个pvc，3个service，3个pod。.........
k8s实践案例-运行zookeeper集群
梵修
09-15 885
查看3个zookeeper的状态，zookeeper为leader，其余节点为follower。再查看zookeeper的状态，zookeeper2已经成为新的leader。将目前的leader停掉，然后验证是否重新选举leader。创建后，查看pod和service。通过脚本执行构建上传镜像。
K8s部署zk集群和kafka集群
热门推荐
qq_25409421的博客
06-24 3万+
本文演示如何在 K8s下部署 Kafka 集群，并且搭建后除了可以从 K8s 内部访问 Kafka 服务，也支持从 K8s 集群外部访问 Kafka 服务。本次我们使用 StatefulSet 方式搭ZooKeeper 集群，使用 Service&Deployment 搭建 Kafka 集群。
k8s环境下安装zookeeper集群并接入springboot项目
溯夜Alex的博客
07-05 337
k8s环境下安装zookeeper集群并接入springboot项目zookeeper集群安装创建存储卷创建zookeeper集群验证zookeeper集群是否启动成功springboot项目接入zookeeper引入依赖yml配置注解启用DemoController zookeeper集群安装 创建存储卷 首先通过nfs创建三个共享目录 mkdir -p /data/share/pv/{zk01,zk02,zk03} 分别对应三节点zk集群中的三个pod的持久化目录，创建好目录之后编写yaml创建zk-
k8s部署zookeeper集群 运行 ZooKeeper， 一个 CP 分布式系统
肥叔菌的博客
01-30 3216
本教程展示了在 Kubernetes 上使用 StatefulSets，PodDisruptionBudgets 和 PodAntiAffinity 特性运行 Apache Zookeeper。 准备开始 在开始本教程前，你应该熟悉以下 Kubernetes 概念：Pods、Cluster DNS、Headless Services、PersistentVolumes、PersistentVolume Provisioning、StatefulSets、PodDisruptionBudgets、PodAnt
（十二）从零开始搭建k8s集群——使用KubeSphere管理平台搭建一个高可用的zookeeper集群服务
厉害哥哥的博客
04-21 3098
ZooKeeper是Apache的一个顶级项目，为分布式应用提供高效、高可用的分布式协调服务，提供了诸如数据发布/订阅、负载均衡、命名服务、分布式协调/通知和分布式锁等分布式基础服务。往期的博客内容我们已经介绍过其作为分布锁的应用案例实战内容，本节内容我们主要介绍一下使用kubesphere平台安装一个k8s环境下高可用的zookeeper集群服务。
以statefulset方式在k8s集群中部署zookeeper3.6.3集群（二）
最美dee时光的博客
09-15 1612
本篇目录链接背景需求分析环境说明1 本文的操作环境为 Kubernetes v1.18.0 版本，使用docker的容器运行时，docker 和 Kubelet 采用的 cgroup 驱动为 systemd。2 采用的是动态存储的方式持久化zk集群的数据准备yaml文件step1：编写zk的配置文件step2：编写zk的pdb文件，保证集群最少可用的节点数step3：编写zk的svc文件step4：编写zk的sts文件step5：依次执行yaml文件 背景 目前我司已经将java程序以微服务的形式迁移到k8
k8s部署zookeeper
w2909526的博客
04-12 246
在创建StatefulSet之前需要有storageClass 这里使用公有云本地盘， 就不列举了。
在k8s上部署 zookeeper + kafka 集群 配置教程
06-13
好的，以下是一个基本的在k8s上部署zookeeper + kafka集群的配置教程： 1. 创建一个namespace 首先，我们需要创建一个namespace，用于部署zookeeper和kafka集群。可以使用以下命令创建一个名为“zookeeper-kafka”...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值