k8s安装MySQL集群问题汇总

@[TOC]k8s安装MySQL集群问题汇总

1、错误0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.

kubectl get pod -A
NAMESPACE              NAME                                         READY   STATUS    RESTARTS   AGE
db                     mysql-0                                      0/2     Pending   0          7m48s
kubectl -n db describe pod mysql-0
Events:
  Type     Reason            Age    From               Message
  ----     ------            ----   ----               -------
  Warning  FailedScheduling  6m55s  default-scheduler  0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.
  Warning  FailedScheduling  6m53s  default-scheduler  0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.
kubectl -n db get pv,pvc
NAME                    CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS     CLAIM             STORAGECLASS   REASON   AGE
persistentvolume/pv-a   2Gi        RWX            Retain           Released   db/data-mysql-0   nfs                     77m
persistentvolume/pv-b   2Gi        RWX            Retain           Released   db/data-mysql-1   nfs                     77m
persistentvolume/pv-c   2Gi        RWX            Retain           Released   db/data-mysql-2   nfs                     77m

NAME                                 STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
persistentvolumeclaim/data-mysql-0   Pending                                      nfs            2m54s

原因:pv状态Released未释放,创建pvc时找不到合适的pv
解决方法:删除pvc,pv,然后重建

kubectl -n db delete pvc data-mysql-0
kubectl -n db delete pv pv-a pv-b pv-c
kubectl -n db describe pod mysql-0
Events:
  Type     Reason            Age    From               Message
  ----     ------            ----   ----               -------
  Warning  FailedScheduling  2m39s  default-scheduler  0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.
  Warning  FailedScheduling  2m37s  default-scheduler  0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims.

kubectl -n db describe pvc

Name:          data-mysql-0
Namespace:     db
StorageClass:  nfs
Status:        Pending
Volume:        
Labels:        app=mysql
               app.kubernetes.io/name=mysql
Annotations:   <none>
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      
Access Modes:  
VolumeMode:    Filesystem
Used By:       mysql-0
Events:
  Type     Reason              Age                    From                         Message
  ----     ------              ----                   ----                         -------
  Warning  ProvisioningFailed  3m11s (x5 over 4m10s)  persistentvolume-controller  storageclass.storage.k8s.io "nfs" not found
  Warning  ProvisioningFailed  7s (x7 over 97s)       persistentvolume-controller  storageclass.storage.k8s.io "nfs" not found

pvc创建失败,检查pv、pvc配置
pv配置:

metadata:
  name: pv-a
spec:
  capacity:
    storage: 2Gi
  accessModes:
  - ReadWriteMany
  persistentVolumeReclaimPolicy: Retain
  storageClassName: nfs
  nfs:
    server: 192.168.216.4
    path: /nfsdata/mysql-01

pvc:配置

- metadata:
      name: data
      namespace: db
    spec:
      accessModes:
      accessModes: ["ReadWriteOnce"]
      storageClassName: nfs
      resources:
        requests:
          storage: 1Gi

原因:pv和pvc accessModes配置不一致,造成创建pvc时找不到合适pv,同时pvc大小不能超过pv大小
解决方法:调整参数一致,删除pvc,pv,然后重建

2、init-mysql CrashLoopBackoff.

kubectl -n db describe pod mysql-0
Events:
  Type     Reason     Age                             From               Message
  ----     ------     ----                            ----               -------
  Normal   Scheduled  3m43s                           default-scheduler  Successfully assigned db/mysql-0 to node02
  Normal   Pulled     <invalid> (x5 over <invalid>)   kubelet            Container image "mysql:5.7" already present on machine
  Normal   Created    <invalid> (x5 over <invalid>)   kubelet            Created container init-mysql
  Normal   Started    <invalid> (x5 over <invalid>)   kubelet            Started container init-mysql
  Warning  BackOff    <invalid> (x10 over <invalid>)  kubelet            Back-off restarting failed container

查看pod mysql-0日志

kubectl -n db logs mysql-0
error: a container name must be specified for pod mysql-0, choose one of: [mysql xtrabackup] or one of the init containers: [init-mysql clone-mysql]
kubectl -n db logs mysql-0 init-mysql
++ hostname
bash: line 5: hostname: command not found
+ [[ '' =~ -([0-9]+)$ ]]
+ exit 1

原因:shell 命令hostname不存在,可能时容器bash问题
解决方法:yaml文件中hostname命令改成环境变量$HOSTNAME

   #[ `hostname` =~ -([0-9]+)$ ]] || exit 1
   [[ $HOSTNAME =~ -([0-9]+)$ ]] || exit 1

删除statefulset后重建

kubectl -n db get pod -o wide
NAME      READY   STATUS    RESTARTS   AGE   IP               NODE     NOMINATED NODE   READINESS GATES
mysql-0   2/2     Running   0          30s   10.122.140.123   node02   <none>           <none>
mysql-1   2/2     Running   0          20s   10.122.140.89    node02   <none>           <none>
mysql-2   1/2     Running   0          9s    10.122.140.90    node02   <none>           <none>
kubectl -n db describe pod
Events:
  Type    Reason     Age        From               Message
  ----    ------     ----       ----               -------
  Normal  Scheduled  64s        default-scheduler  Successfully assigned db/mysql-2 to node02
  Normal  Pulled     <invalid>  kubelet            Container image "mysql:5.7" already present on machine
  Normal  Created    <invalid>  kubelet            Created container init-mysql
  Normal  Started    <invalid>  kubelet            Started container init-mysql
  Normal  Pulled     <invalid>  kubelet            Container image "gcr.io/google-samples/xtrabackup:1.0" already present on machine
  Normal  Created    <invalid>  kubelet            Created container clone-mysql
  Normal  Started    <invalid>  kubelet            Started container clone-mysql
  Normal  Pulled     <invalid>  kubelet            Container image "mysql:5.7" already present on machine
  Normal  Created    <invalid>  kubelet            Created container mysql
  Normal  Started    <invalid>  kubelet            Started container mysql
  Normal  Pulled     <invalid>  kubelet            Container image "gcr.io/google-samples/xtrabackup:1.0" already present on machine
  Normal  Created    <invalid>  kubelet            Created container xtrabackup
  Normal  Started    <invalid>  kubelet            Started container xtrabackup

k8s MySQL集群创建完成。

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


学习编程是顺着互联网的发展潮流,是一件好事。新手如何学习编程?其实不难,不过在学习编程之前你得先了解你的目的是什么?这个很重要,因为目的决定你的发展方向、决定你的发展速度。
IT行业是什么工作做什么?IT行业的工作有:产品策划类、页面设计类、前端与移动、开发与测试、营销推广类、数据运营类、运营维护类、游戏相关类等,根据不同的分类下面有细分了不同的岗位。
女生学Java好就业吗?女生适合学Java编程吗?目前有不少女生学习Java开发,但要结合自身的情况,先了解自己适不适合去学习Java,不要盲目的选择不适合自己的Java培训班进行学习。只要肯下功夫钻研,多看、多想、多练
Can’t connect to local MySQL server through socket \'/var/lib/mysql/mysql.sock问题 1.进入mysql路径
oracle基本命令 一、登录操作 1.管理员登录 # 管理员登录 sqlplus / as sysdba 2.普通用户登录
一、背景 因为项目中需要通北京网络,所以需要连vpn,但是服务器有时候会断掉,所以写个shell脚本每五分钟去判断是否连接,于是就有下面的shell脚本。
BETWEEN 操作符选取介于两个值之间的数据范围内的值。这些值可以是数值、文本或者日期。
假如你已经使用过苹果开发者中心上架app,你肯定知道在苹果开发者中心的web界面,无法直接提交ipa文件,而是需要使用第三方工具,将ipa文件上传到构建版本,开...
下面的 SQL 语句指定了两个别名,一个是 name 列的别名,一个是 country 列的别名。**提示:**如果列名称包含空格,要求使用双引号或方括号:
在使用H5混合开发的app打包后,需要将ipa文件上传到appstore进行发布,就需要去苹果开发者中心进行发布。​
+----+--------------+---------------------------+-------+---------+
数组的声明并不是声明一个个单独的变量,比如 number0、number1、...、number99,而是声明一个数组变量,比如 numbers,然后使用 nu...
第一步:到appuploader官网下载辅助工具和iCloud驱动,使用前面创建的AppID登录。
如需删除表中的列,请使用下面的语法(请注意,某些数据库系统不允许这种在数据库表中删除列的方式):
前不久在制作win11pe,制作了一版,1.26GB,太大了,不满意,想再裁剪下,发现这次dism mount正常,commit或discard巨慢,以前都很快...
赛门铁克各个版本概览:https://knowledge.broadcom.com/external/article?legacyId=tech163829
实测Python 3.6.6用pip 21.3.1,再高就报错了,Python 3.10.7用pip 22.3.1是可以的
Broadcom Corporation (博通公司,股票代号AVGO)是全球领先的有线和无线通信半导体公司。其产品实现向家庭、 办公室和移动环境以及在这些环境...
发现个问题,server2016上安装了c4d这些版本,低版本的正常显示窗格,但红色圈出的高版本c4d打开后不显示窗格,
TAT:https://cloud.tencent.com/document/product/1340