tiup部署check问题

#cluster check ./deploy.yaml --user tidb

os-version Fail Ubuntu 16.04 LTS 16.04 not supported, use version 18.04 or higher (ubuntu support is not fully tested, be careful)
cpu-cores Pass number of CPU cores / threads: 24
memory Pass memory size is 131072MB
network Pass network speed of eth0 is 10000MB
network Pass network speed of eth1 is 10000MB
disk Fail mount point / does not have ‘nodelalloc’ option set
disk Warn mount point / does not have ‘noatime’ option set
disk Fail mount point / does not have ‘nodelalloc’ option set
disk Warn mount point / does not have ‘noatime’ option set
limits Fail soft limit of ‘nofile’ for user ‘tidb’ is not set or too low
limits Fail hard limit of ‘nofile’ for user ‘tidb’ is not set or too low
limits Fail soft limit of ‘stack’ for user ‘tidb’ is not set or too low
sysctl Fail net.core.somaxconn = 1024, should be greater than 32768
sysctl Fail net.ipv4.tcp_syncookies = 1, should be 0
sysctl Fail vm.swappiness = 10, should be 0
selinux Pass SELinux is disabled
thp Fail THP is enabled, please disable it for best performance
service Fail service irqbalance not found, should be installed and started
service Pass service firewalld not found, ignore
command Pass numactl: policy: default

有几个疑问:
1)Ubuntu 16.04 LTS 16.04 not supported 是怎么回事? 不支持吗 还是说某些tidb版本不支持16.04?
2)如果用–apply修复的话,会不会重新mount挂载点,这样会有很大的风险
3)所有的Fail状态的 指定了–apply都会修复吗?

版本
出现的问题
可复现操作
脚本
日志
有些信息缺失的麻烦补充一下~

https://docs.pingcap.com/zh/tidb/stable/production-deployment-using-tiup


看着官方文档安装而已

试了 指定–apply参数,disk挂载不会修复,但是limits和sysctl 会被修复

在运行检测时,若指定了 --apply 参数,程序将尝试对其中未通过的项目自动修复。自动修复仅限于部分可通过修改配置或系统参数调整的项目,其它未修复的项目需要根据实际情况手工处理。

1 个赞

谢谢 @hey-hoho,请教下tiup安装后的组件,但是手工kill某个实例后,比如 tidb-server A实例后,过几分钟tidb-server实例会被拉起来,怎样禁止掉自动拉起呢?

systemctl disable tidb-4000.service关闭自动重启。
不过还是建议你使用tiup scale-in缩容方式下线不需要的节点。

1 个赞

我已经关闭了
system disable pd-4000.service
但是过2分钟 貌似还会自动被重启

我kill掉所有的pd节点(确切的说是通过 rm -rf pd-2379 ),发现pd-server会自动重启
$ systemctl status pd-2379.service
● pd-2379.service - pd service
Loaded: loaded (/etc/systemd/system/pd-2379.service; disabled; vendor preset: enabled)
Active: active (running) since Fri 2021-10-08 19:15:37 CST; 8s ago
Main PID: 41003 (pd-server)
Tasks: 23
Memory: 41.1M
CPU: 316ms
CGroup: /system.slice/pd-2379.service

那去/etc/systemd/system下面改一下对应service的重启策略吧

$ cat /etc/systemd/system/pd-2379.service
[Unit]
Description=pd service
After=syslog.target network.target remote-fs.target nss-lookup.target

[Service]
LimitNOFILE=1000000
LimitSTACK=10485760
User=tidb
ExecStart=/data/tidb/tidb-deploy/pd-2379/scripts/run_pd.sh
Restart=no

[Install]
WantedBy=multi-user.target

修改成这样后,然后rm -rf pd-2379 三个实例后,还是被拉起了,好奇怪

@hey-hoho

这个问题辛苦整理一下新开个帖子提问吧,方便其他人搜索相同的问题,tiup check的问题已经解决了。

修改/etc/systemd/system/pd-2379.service 后需要
systemctl daemon-reload
发现pd就不会被拉起了

主要对systemctl不熟悉

是的,改了service后要reload生效

此话题已在最后回复的 1 分钟后被自动关闭。不再允许新回复。