版本 v3.0.7
架构类型 3TiDB混部3PD 3TiKV(双实例)
业务在进行集群高可用性、数据是否正常的测试时候,启停顺序如下
ansible-playbook stop.yml -l TIDB1
ansible-playbook stop.yml -l PD3
ansible-playbook stop.yml -l TiKV1-1
ansible-playbook stop.yml -l TiKV1-2
ansible-playbook start.yml -l TiKV1-2
ansible-playbook start.yml -l TiKV1-1
ansible-playbook start.yml -l PD3
ansible-playbook start.yml -l TIDB1
业务反馈说
「 到这一步才报错 ansible-playbook start.yml -l TIDB1 」
接手问题的时候的情况为 TiDB1一直无法启动成功 进程无法拉起,其余节点已经拉起:
TiDB1使用 start.yml脚本、tidb部署目录的start脚本、也使用systemctl 启动过tidb-4000.service都没有启动成功。
当前未启动的TiDB1 错误日志 如下
time=“2020-07-31T19:09:27+08:00” level=fatal msg=“Near line 31 (last key parsed ‘performance’): expected a top-level item to end with a newline, comment, or EOF, but got ‘G’ instead”
time=“2020-07-31T19:09:42+08:00” level=fatal msg=“Near line 31 (last key parsed ‘performance’): expected a top-level item to end with a newline, comment, or EOF, but got ‘G’ instead”
time=“2020-07-31T19:09:58+08:00” level=fatal msg=“Near line 31 (last key parsed ‘performance’): expected a top-level item to end with a newline, comment, or EOF, but got ‘G’ instead”
time=“2020-07-31T19:10:13+08:00” level=fatal msg=“Near line 31 (last key parsed ‘performance’): expected a top-level item to end with a newline, comment, or EOF, but got ‘G’ instead”
time=“2020-07-31T19:10:28+08:00” level=fatal msg=“Near line 31 (last key parsed ‘performance’): expected a top-level item to end with a newline, comment, or EOF, but got ‘G’ instead”
time=“2020-07-31T19:10:43+08:00” level=fatal msg=“Near line 31 (last key parsed ‘performance’): expected a top-level item to end with a newline, comment, or EOF, but got ‘G’ instead”
time=“2020-07-31T19:10:59+08:00” level=fatal msg=“Near line 31 (last key parsed ‘performance’): expected a top-level item to end with a newline, comment, or EOF, but got ‘G’ instead”
测试过的方法:stop tidb后再启动start也没有成功
最后生效拉起的方法:ansible-playbook rolling_update.yml -l PD1,TiDB1
麻烦分析一下宕节点之后启动失败的原因