TiDB Binlog 部署拓扑

来了老弟 · 2021 年3 月 11 日 09:06

tiup.zip (5.9 MB) tiup-cluster.zip (7.2 MB)

tiup 替换 ~/.tiup/bin/tiup
tiup-cluster 替换 /home/tidb/.tiup/components/cluster/v1.3.4/tiup-cluster

YouCD · 2021 年3 月 11 日 09:39

不行在这个已经安全加固的环境下 ,只是不知道是什么原因导致无法部署成功

检查md5

salt -L "172.16.12.141,172.16.12.218,172.16.12.204,172.16.12.165,172.16.12.156,172.16.12.175,172.16.12.203,172.16.12.211,172.16.12.173,172.16.12.159,172.16.12.146,172.16.12.131,172.16.12.214" cmd.run "md5sum /home/tidb/.tiup/components/cluster/v1.3.4/*"
172.16.12.214:
    md5sum: /home/tidb/.tiup/components/cluster/v1.3.4/*: No such file or directory
172.16.12.146:
    6e32bfc5da4e9e630105c53438a754a5  /home/tidb/.tiup/components/cluster/v1.3.4/tiup-cluster
172.16.12.204:
    6e32bfc5da4e9e630105c53438a754a5  /home/tidb/.tiup/components/cluster/v1.3.4/tiup-cluster
172.16.12.131:
    6e32bfc5da4e9e630105c53438a754a5  /home/tidb/.tiup/components/cluster/v1.3.4/tiup-cluster
172.16.12.159:
    6e32bfc5da4e9e630105c53438a754a5  /home/tidb/.tiup/components/cluster/v1.3.4/tiup-cluster
172.16.12.165:
    6e32bfc5da4e9e630105c53438a754a5  /home/tidb/.tiup/components/cluster/v1.3.4/tiup-cluster
172.16.12.173:
    6e32bfc5da4e9e630105c53438a754a5  /home/tidb/.tiup/components/cluster/v1.3.4/tiup-cluster
172.16.12.203:
    6e32bfc5da4e9e630105c53438a754a5  /home/tidb/.tiup/components/cluster/v1.3.4/tiup-cluster
172.16.12.218:
    6e32bfc5da4e9e630105c53438a754a5  /home/tidb/.tiup/components/cluster/v1.3.4/tiup-cluster
172.16.12.211:
    6e32bfc5da4e9e630105c53438a754a5  /home/tidb/.tiup/components/cluster/v1.3.4/tiup-cluster
172.16.12.156:
    6e32bfc5da4e9e630105c53438a754a5  /home/tidb/.tiup/components/cluster/v1.3.4/tiup-cluster
172.16.12.141:
    6e32bfc5da4e9e630105c53438a754a5  /home/tidb/.tiup/components/cluster/v1.3.4/tiup-cluster
172.16.12.175:
    6e32bfc5da4e9e630105c53438a754a5  /home/tidb/.tiup/components/cluster/v1.3.4/tiup-cluster

部署过程

tiup cluster deploy --user=root daddylab-tidb-cluster v4.0.11 complex-tidb-binlog.yaml
Starting component `cluster`: /root/.tiup/components/cluster/v1.3.4/tiup-cluster deploy --user=root daddylab-tidb-cluster v4.0.11 complex-tidb-binlog.yaml
Please confirm your topology:
Cluster type:    tidb
Cluster name:    daddylab-tidb-cluster
Cluster version: v4.0.11
Type          Host           Ports        OS/Arch       Directories
----          ----           -----        -------       -----------
pd            172.16.12.159  2379/2380    linux/x86_64  /tidb-deploy/pd-2379,/tidb-data/pd-2379
pd            172.16.12.173  2379/2380    linux/x86_64  /tidb-deploy/pd-2379,/tidb-data/pd-2379
pd            172.16.12.211  2379/2380    linux/x86_64  /tidb-deploy/pd-2379,/tidb-data/pd-2379
tikv          172.16.12.214  20160/20180  linux/x86_64  /tidb-deploy/tikv-20160,/tidb-data/tikv-20160
tikv          172.16.12.131  20160/20180  linux/x86_64  /tidb-deploy/tikv-20160,/tidb-data/tikv-20160
tikv          172.16.12.146  20160/20180  linux/x86_64  /tidb-deploy/tikv-20160,/tidb-data/tikv-20160
pump          172.16.12.165  8250         linux/x86_64  /tidb-deploy/pump-8249,/tidb-data/pump-8249
pump          172.16.12.218  8250         linux/x86_64  /tidb-deploy/pump-8249,/tidb-data/pump-8249
pump          172.16.12.204  8250         linux/x86_64  /tidb-deploy/pump-8249,/tidb-data/pump-8249
tidb          172.16.12.203  4000/10080   linux/x86_64  /tidb-deploy/tidb-4000
tidb          172.16.12.175  4000/10080   linux/x86_64  /tidb-deploy/tidb-4000
tidb          172.16.12.156  4000/10080   linux/x86_64  /tidb-deploy/tidb-4000
drainer       172.16.12.141  8249         linux/x86_64  /tidb-deploy/drainer-8249,/tidb-data/drainer-8249
prometheus    172.16.12.141  9090         linux/x86_64  /tidb-deploy/prometheus-9090,/tidb-data/prometheus-9090
grafana       172.16.12.141  3000         linux/x86_64  /tidb-deploy/grafana-3000
alertmanager  172.16.12.141  9093/9094    linux/x86_64  /tidb-deploy/alertmanager-9093,/tidb-data/alertmanager-9093
Attention:
    1. If the topology is not what you expected, check your yaml file.
    2. Please confirm there is no port/directory conflicts in same host.
Do you want to continue? [y/N]:  y
+ Generate SSH keys ... Done
+ Download TiDB components
  - Download pd:v4.0.11 (linux/amd64) ... Done
  - Download tikv:v4.0.11 (linux/amd64) ... Done
  - Download pump:v4.0.11 (linux/amd64) ... Done
  - Download tidb:v4.0.11 (linux/amd64) ... Done
  - Download drainer:v4.0.11 (linux/amd64) ... Done
  - Download prometheus:v4.0.11 (linux/amd64) ... Done
  - Download grafana:v4.0.11 (linux/amd64) ... Done
  - Download alertmanager: (linux/amd64) ... Done
  - Download node_exporter: (linux/amd64) ... Done
  - Download blackbox_exporter: (linux/amd64) ... Done
+ Initialize target host environments
  - Prepare 172.16.12.159:22 ... ⠸ EnvInit: user=tidb, host=172.16.12.159
  - Prepare 172.16.12.173:22 ... ⠸ EnvInit: user=tidb, host=172.16.12.173
  - Prepare 172.16.12.211:22 ... ⠸ EnvInit: user=tidb, host=172.16.12.211
  - Prepare 172.16.12.214:22 ... ⠸ EnvInit: user=tidb, host=172.16.12.214
  - Prepare 172.16.12.131:22 ... ⠸ EnvInit: user=tidb, host=172.16.12.131
  - Prepare 172.16.12.146:22 ... ⠸ EnvInit: user=tidb, host=172.16.12.146
  - Prepare 172.16.12.165:22 ... ⠸ EnvInit: user=tidb, host=172.16.12.165
  - Prepare 172.16.12.218:22 ... ⠸ EnvInit: user=tidb, host=172.16.12.218
  - Prepare 172.16.12.204:22 ... ⠸ EnvInit: user=tidb, host=172.16.12.204
  - Prepare 172.16.12.203:22 ... ⠸ EnvInit: user=tidb, host=172.16.12.203
  - Prepare 172.16.12.175:22 ... ⠸ EnvInit: user=tidb, host=172.16.12.175
  - Prepare 172.16.12.156:22 ... ⠸ EnvInit: user=tidb, host=172.16.12.156
  - Prepare 172.16.12.141:22 ... ⠸ EnvInit: user=tidb, host=172.16.12.141
panic: send on closed channel

goroutine 662 [running]:
github.com/appleboy/easyssh-proxy.(*MakeConfig).Stream.func1.1(0xc000a5bc80, 0xc0008f26c0, 0xc00024dc70)
	github.com/appleboy/easyssh-proxy@v1.3.2/easyssh.go:255 +0x7c
created by github.com/appleboy/easyssh-proxy.(*MakeConfig).Stream.func1
	github.com/appleboy/easyssh-proxy@v1.3.2/easyssh.go:253 +0x285
Error: run `/root/.tiup/components/cluster/v1.3.4/tiup-cluster` (wd:/root/.tiup/data/SRL9ynE) failed: exit status 2

tiup 版本信息

md5sum `which tiup`
fdaa65d9ea298285b4e1cf1d567fa8dd  /root/.tiup/bin/tiup
[root@tidb-cluster-tidb1 install]# tiup -v
tiup version 1.3.4 tiup
Go Version: go1.16.1
Git Ref: master
GitHash: 7076c6c

总结

先非常感谢耽搁您宝贵的时间来的答疑
目前我已经用未安全加固的环境下部署成功，正在测试TiDB相关功能
我的这个环境可能也是个例，无需在花时间在这上面
如果仍想继续在此环境测试tiup 我会保留该环境，配合直至找出最终的原因

非常感谢耽搁您宝贵的时间来的答疑！！

yilong · 2021 年3 月 11 日 09:57

感谢反馈，看来要先部署，再安全加固比较好

来了老弟 · 2021 年3 月 15 日 03:31

你好，从报错信息来看，怀疑 tiup-cluster bin 文件并没被确替换，

辛苦按照这个方式在进行替换并 deploy 操作。

如有报错辛苦展示报错信息、tiup --version && tiup cluster --version 确认版本

期待你的反馈~

system · 2022 年10 月 31 日 19:08

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