TiUniManager安装的疑惑


1.你要使用TIUP_HOME=/home/tidb/.tiup tiup mirror set tidb-enterprise-server-v6.1.0-linux-amd64命令更改为6.1.0的镜像,我看你发的图片还是没改成功
2.选择在接管集群里面导入主机和主机管理导入主机的主要区别就是减少对主机的检测

这个我是改成功了的,我只是把tidb-server那个离线包解压缩之后重命名为tidb-repo了

总感觉你的filebeat组件出问题了,你的是测试环境吗
你按我发的文档重新搭一个会更快解决

1 个赞

我是测试环境

您说的是这个文档吧:https://tidb.net/blog/9fb1de13

如果是filebeat有问题,那就可能是我下载的离线安装包有问题,我重新下载一个试试。
另外,您发我的那个文档和官方文档一样,有这么一步:
TIUP_HOME=/home/tidb/.tiup tiup mirror merge tidb-enterprise-server-${version}-linux-amd64
他用的是merge,目前来看merge肯定是报错的

只能set,这样就只能来回切了,两个merror

你把tidb-enterprise-server-${version}-linux-amd64目录里面keys复制到~/.tiup/里面,
然后set设置为tidb-enterprise-server-${version}-linux-amd64就可以了,不用来回切

是的 按这个文档安装下,文档里面有安装包下载地址,可以重新下载试试,你跟着文档走,应该不用set设置mirror,show应该也是显示你的tidb-enterprise-server-${version}-linux-amd64目录的

这个问题好了,还真是下载的包有问题。
现在有个新问题,麻烦帮忙看看,如下图所示:

补充上面一条,这两个机器干干净的,啥都没部署,一个正常一个库存不足确实很奇怪:

再补充,如下是clusterserver的日志,我格式化了一下:
[{
“componentType”: “PD”,
“componentName”: “PD”,
“zoneCode”: “Region1,Zone1_1”,
“diskType”: “SATA”,
“diskCapacity”: 0,
“specCode”: “24C64G”,
“count”: 1,
“hostIp”: “10.0.42.166”,
“diskId”: “”,
“enough”: true
}, {
“componentType”: “PD”,
“componentName”: “PD”,
“zoneCode”: “Region1,Zone1_1”,
“diskType”: “SATA”,
“diskCapacity”: 0,
“specCode”: “24C64G”,
“count”: 1,
“hostIp”: “10.0.6.42”,
“diskId”: “”,
“enough”: true
}, {
“componentType”: “PD”,
“componentName”: “PD”,
“zoneCode”: “Region1,Zone1_1”,
“diskType”: “SATA”,
“diskCapacity”: 0,
“specCode”: “24C64G”,
“count”: 1,
“hostIp”: “10.0.6.43”,
“diskId”: “”,
“enough”: true
}, {
“componentType”: “TiDB”,
“componentName”: “TiDB”,
“zoneCode”: “Region1,Zone1_1”,
“diskType”: “SATA”,
“diskCapacity”: 0,
“specCode”: “32C64G”,
“count”: 1,
“hostIp”: “10.0.42.208”,
“diskId”: “”,
“enough”: true
}, {
“componentType”: “TiDB”,
“componentName”: “TiDB”,
“zoneCode”: “Region1,Zone1_1”,
“diskType”: “SATA”,
“diskCapacity”: 0,
“specCode”: “32C64G”,
“count”: 1,
“hostIp”: “10.0.42.209”,
“diskId”: “”,
“enough”: true
}, {
“componentType”: “TiKV”,
“componentName”: “TiKV”,
“zoneCode”: “Region1,Zone1_1”,
“diskType”: “SATA”,
“diskCapacity”: 0,
“specCode”: “32C96G”,
“count”: 1,
“hostIp”: “10.0.42.210”,
“diskId”: “3BMdm8QhQ3uqNFX_BMgHTA”,
“enough”: true
}, {
“componentType”: “TiKV”,
“componentName”: “TiKV”,
“zoneCode”: “Region1,Zone1_1”,
“diskType”: “SATA”,
“diskCapacity”: 0,
“specCode”: “32C96G”,
“count”: 1,
“hostIp”: “10.0.42.211”,
“diskId”: “kG4vtWXBQXOtghpXm4X4kA”,
“enough”: true
}, {
“componentType”: “TiKV”,
“componentName”: “TiKV”,
“zoneCode”: “Region1,Zone1_1”,
“diskType”: “SATA”,
“diskCapacity”: 0,
“specCode”: “32C96G”,
“count”: 1,
“hostIp”: “10.0.42.212”,
“diskId”: “2W_5W0YWQhqNhP3L1OSuvQ”,
“enough”: true
}, {
“componentType”: “TiFlash”,
“componentName”: “TiFlash”,
“zoneCode”: “Region1,Zone1_1”,
“diskType”: “SATA”,
“diskCapacity”: 0,
“specCode”: “24C64G”,
“count”: 1,
“hostIp”: “10.0.42.213”,
“diskId”: “ZomqQrBzTgWTDVe3Qa96Cw”,
“enough”: true
}, {
“componentType”: “TiFlash”,
“componentName”: “TiFlash”,
“zoneCode”: “Region1,Zone1_1”,
“diskType”: “SATA”,
“diskCapacity”: 0,
“specCode”: “24C64G”,
“count”: 1,
“hostIp”: “10.0.42.213”,
“diskId”: “3p2FaOb-Qamkbj5wZDBpFQ”,
“enough”: true
}, {
“componentType”: “TiFlash”,
“componentName”: “TiFlash”,
“zoneCode”: “Region1,Zone1_1”,
“diskType”: “SATA”,
“diskCapacity”: 0,
“specCode”: “24C64G”,
“count”: 1,
“hostIp”: “10.0.42.214”,
“diskId”: “9nTlO4XESBKW8qmjkjxmGg”,
“enough”: false
}, {
“componentType”: “TiFlash”,
“componentName”: “TiFlash”,
“zoneCode”: “Region1,Zone1_1”,
“diskType”: “SATA”,
“diskCapacity”: 0,
“specCode”: “24C64G”,
“count”: 1,
“hostIp”: “10.0.42.214”,
“diskId”: “wMGp8cYQT6ix5O0RPjG1EA”,
“enough”: false
}]

日志显示“enough”: false,你导入主机的模板怎么配的?

对比下两台机器配置是否一样,修改下导入主机模板,删除主机再重试

两台机器配置一模一样,附件是我的模板,最后那两行就是那两台机器
hostInfo_template.xlsx (10.7 KB)

重新导入多少次都是库存不足

那两台机器原来分量快盘,怎么都不行,我放弃了,干脆两块盘合成一块盘就不报库存问题了,不过部署集群的时候报磁盘空间不足,新的机器,每个节点几百G磁盘空间,不应该不足啊。
disk is not enough

试一下先部署tidb,pd,tikv这3种节点试试,然后再扩容排查下问题

现在是已经导入成功了吧

导入成功了,一直报disk is not enough

看一下是不是 PD 里面的 TiKV 磁盘阈值设置的问题和 Store 里面磁盘的空间是不是两块盘合并的大小吧。