【概述】 场景 + 问题概述
停机升级
tiup v5.4.2升级到 6.40 启动报错
tiup cluster upgrade ak-tidb-cluster v6.4.0 --offline
应该是5.4的tikv版本不支持直接升级到6.4,如果测试环境的话可以先升级到6.2 在试试
现在已经有一部分升级到6.4了 怎么处理呢
哪些组件
3个tidb&PD混部,版本信息,其中 TiKV Min Version: 6.2.0-alpha
Release Version: v6.4.0
Edition: Community
Git Commit Hash: cf36a9ce2fe1039db3cf3444d51930b887df18a1
Git Branch: heads/refs/tags/v6.4.0
UTC Build Time: 2022-11-13 05:25:30
GoVersion: go1.19.2
Race Enabled: false
TiKV Min Version: 6.2.0-alpha
Check Table Before Drop: false
Store: unistore
Release Version: v6.4.0
Edition: Community
Git Commit Hash: cf36a9ce2fe1039db3cf3444d51930b887df18a1
Git Branch: heads/refs/tags/v6.4.0
UTC Build Time: 2022-11-13 05:25:30
GoVersion: go1.19.2
Race Enabled: false
TiKV Min Version: 6.2.0-alpha
Check Table Before Drop: false
Store: unistore
Release Version: v6.4.0
Edition: Community
Git Commit Hash: cf36a9ce2fe1039db3cf3444d51930b887df18a1
Git Branch: heads/refs/tags/v6.4.0
UTC Build Time: 2022-11-13 05:25:30
GoVersion: go1.19.2
Race Enabled: false
TiKV Min Version: 6.2.0-alpha
Check Table Before Drop: false
Store: unistore
4个tikv节点版本信息
TiKV
Release Version: 6.4.0
Edition: Community
Git Commit Hash: af4c732c46ef62e677266e0055e2a8b50207f09c
Git Commit Branch: heads/refs/tags/v6.4.0
UTC Build Time: 2022-11-09 06:27:32
Rust Version: rustc 1.64.0-nightly (0f4bcadb4 2022-07-30)
Enable Features: pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine cloud-aws cloud-gcp cloud-azure
Profile: dist_release
TiKV
Release Version: 6.4.0
Edition: Community
Git Commit Hash: af4c732c46ef62e677266e0055e2a8b50207f09c
Git Commit Branch: heads/refs/tags/v6.4.0
UTC Build Time: 2022-11-09 06:27:32
Rust Version: rustc 1.64.0-nightly (0f4bcadb4 2022-07-30)
Enable Features: pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine cloud-aws cloud-gcp cloud-azure
Profile: dist_release
TiKV
Release Version: 6.4.0
Edition: Community
Git Commit Hash: af4c732c46ef62e677266e0055e2a8b50207f09c
Git Commit Branch: heads/refs/tags/v6.4.0
UTC Build Time: 2022-11-09 06:27:32
Rust Version: rustc 1.64.0-nightly (0f4bcadb4 2022-07-30)
Enable Features: pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine cloud-aws cloud-gcp cloud-azure
Profile: dist_release
TiKV
Release Version: 6.4.0
Edition: Community
Git Commit Hash: af4c732c46ef62e677266e0055e2a8b50207f09c
Git Commit Branch: heads/refs/tags/v6.4.0
UTC Build Time: 2022-11-09 06:27:32
Rust Version: rustc 1.64.0-nightly (0f4bcadb4 2022-07-30)
Enable Features: pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine cloud-aws cloud-gcp cloud-azure
Profile: dist_release
是不是 tikv 升级的过程中有点问题,没有完全升级成功?
你可以详细描述你的升级流程吗?
tikv为啥是4个
tiup 版本
[tidb@tikv1 ~]$ tiup --version
1.11.1 tiup
Go Version: go1.19.2
Git Ref: v1.11.1
GitHash: b95172df211e4f9b643590f2dd8436ad60c72b38
有一个tikv后续要准备缩容掉
请问 tiup cluster display 输出什么?
看起来 TiKV 已经升级到 6.4.0 了,TiDB 不应该再报错
所以现在集群节点都是没启动的状态吗? 还有其他error log吗?
tikv和pd服务 start后是up的,tidb启动不了,一直报那个错误。
嗯 看上去升级ok的,但确实有问题,
tiup cluster display asinking-tidb-cluster 正常吗?不行再升级一次?
不行的还是那个问题
新扩容一个tidb节点试试呢,先把服务跑起来。6.4是DMR版本,问题可能会比较多。
tiup cluster display的全部信息贴下
tiup cluster display asinking-tidb-cluster 结果贴一下,敏感信息可以打码