Linux下自建tidb6.1.1单节点搭建

最新推荐文章于 2025-01-25 10:11:56 发布
最新推荐文章于 2025-01-25 10:11:56 发布
阅读量575 收藏 1
点赞数 1
文章标签： linux 运维 服务器 tidb mysql 数据库 centos
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/huangsu_123/article/details/134142155
版权

环境：centos7+mysql8.0.16

一、搭建mysql服务：

mysql8.0.16单节点搭建

二、下载tidb社区版安装包：

tidb社区版安装包

三、环境准备：

1、安装工具numactl

yum -y install numactl

2、修改sysctl参数：

echo "fs.file-max = 1000000">> /etc/sysctl.conf
echo "net.core.somaxconn = 32768">> /etc/sysctl.conf
echo "net.ipv4.tcp_tw_recycle = 0">> /etc/sysctl.conf
echo "net.ipv4.tcp_syncookies = 0">> /etc/sysctl.conf
echo "vm.overcommit_memory = 1">> /etc/sysctl.conf
sysctl -p #查看参数

3、配置/etc/security/limits.conf文件(文件最后追加)：

vi /etc/security/limits.conf
tidb           soft    nofile          1000000
tidb           hard    nofile          1000000
tidb           soft    stack          32768
tidb           hard    stack          32768

4、修改配置文件(文件最后追加)：

vi /etc/rc.local
if test -f /sys/kernel/mm/transparent_hugepage/enabled; then
echo never > /sys/kernel/mm/transparent_hugepage/enabled
fi
chmod +x /etc/rc.local
source /etc/rc.local

5、ssh免密登录：

mkdir ~/.ssh
chmod 700 ~/.ssh
ssh-keygen -t rsa #三个回车
ssh-keygen -t dsa #三个回车
cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys

6、新建tidb组和tidb用户

groupadd tidb
useradd -g tidb tidb

四、安装tidb：

1、创建文件夹存放tidb文件，并解压tidb压缩包：

mkdir /tidb
tar -xvf /tidb/tidb-community-server-v6.1.1-linux-amd64.tar.gz -C /tidb

 2、部署tiup：

sh /tidb/tidb-community-server-v6.1.1-linux-amd64/local_install.sh
source /root/.bash_profile
[root@localhost tidb]# sh /tidb/tidb-community-server-v6.1.1-linux-amd64/local_install.sh
Disable telemetry success
Successfully set mirror to /tidb/tidb-community-server-v6.1.1-linux-amd64
Detected shell: bash
Shell profile:  /root/.bash_profile
/root/.bash_profile has been modified to to add tiup to PATH
open a new terminal or source /root/.bash_profile to use it
Installed path: /root/.tiup/bin/tiup
===============================================
1. source /root/.bash_profile
2. Have a try:   tiup playground
===============================================
[root@localhost tidb]# source /root/.bash_profile
[root@localhost tidb]# which tiup
/root/.tiup/bin/tiup

3、生成初始化拓扑模板：

 tiup cluster template > /tidb/topology.yaml

 4、修改模版(可将/tidb/topology.yaml文件里面的内容全部删除，替换成下面的，也可以只改文件中的ip)：

vi /tidb/topology.yaml
global:
  user: "tidb"
  ssh_port: 22
  deploy_dir: "/tidb-deploy"
  data_dir: "/tidb-data"
server_configs: {}
pd_servers:
  - host: 192.168.200.57
tidb_servers:
  - host: 192.168.200.57
tikv_servers:
  - host: 192.168.200.57
monitoring_servers:
  - host: 192.168.200.57
grafana_servers:
  - host: 192.168.200.57
alertmanager_servers:
  - host: 192.168.200.57
tiflash_servers:
    - host: 192.168.200.57

5、检查是否瞒住tidb条件：

tiup cluster check /tidb/topology.yaml

这一步检查报ssh错误，tidb没有可执行权限：

执行yum -y update即可解决。

报下面的错误可以忽略，因为我用到的存储空间很少很少，若正常情况，需要进行扩容，将tikv和tiflash的存储路径放在不同目录(即修改/tidb/topology.yaml里面数据存储的目录的参数)。

[root@localhost ~]# tiup cluster check /tidb/topology.yaml
tiup is checking updates for component cluster ...
Starting component `cluster`: /root/.tiup/components/cluster/v1.10.3/tiup-cluster check /tidb/topology.yaml

+ Detect CPU Arch Name
  - Detecting node 192.168.200.57 Arch info ... Done

+ Detect CPU OS Name
  - Detecting node 192.168.200.57 OS info ... Done
+ Download necessary tools
  - Downloading check tools for linux/amd64 ... Done
+ Collect basic system information
+ Collect basic system information
  - Getting system info of 192.168.200.57:22 ... Done
+ Check time zone
  - Checking node 192.168.200.57 ... Done
+ Check system requirements
+ Check system requirements
+ Check system requirements
+ Check system requirements
  - Checking node 192.168.200.57 ... Done
  - Checking node 192.168.200.57 ... Done
  - Checking node 192.168.200.57 ... Done
  - Checking node 192.168.200.57 ... Done
  - Checking node 192.168.200.57 ... Done
  - Checking node 192.168.200.57 ... Done
  - Checking node 192.168.200.57 ... Done
+ Cleanup check files
  - Cleanup check files on 192.168.200.57:22 ... Done
  - Cleanup check files on 192.168.200.57:22 ... Done
  - Cleanup check files on 192.168.200.57:22 ... Done
  - Cleanup check files on 192.168.200.57:22 ... Done
  - Cleanup check files on 192.168.200.57:22 ... Done
  - Cleanup check files on 192.168.200.57:22 ... Done
  - Cleanup check files on 192.168.200.57:22 ... Done
Node            Check            Result  Message
----            -----            ------  -------
192.168.200.57  disk             Warn    mount point / does not have 'noatime' option set
192.168.200.57  disk             Fail    multiple components tikv:/tidb-data/tikv-20160,tiflash:/tidb-data/tiflash-9000 are using the same partition 192.168.200.57:/ as data dir
192.168.200.57  sysctl           Fail    vm.swappiness = 30, should be 0
192.168.200.57  selinux          Pass    SELinux is disabled
192.168.200.57  thp              Fail    THP is enabled, please disable it for best performance
192.168.200.57  cpu-cores        Pass    number of CPU cores / threads: 2
192.168.200.57  memory           Pass    memory size is 4096MB
192.168.200.57  epoll-exclusive  Fail    epoll exclusive is not supported
192.168.200.57  command          Pass    numactl: policy: default
192.168.200.57  network          Pass    network speed of eno16777984 is 10000MB
192.168.200.57  os-version       Pass    OS is CentOS Linux 7 (Core) 7.9.2009
192.168.200.57  cpu-governor     Warn    Unable to determine current CPU frequency governor policy
192.168.200.57  swap             Warn    swap is enabled, please disable it for best performance

6、安装tidb：

tiup cluster deploy mytidb_cluster v6.1.1 /tidb/topology.yaml

[root@localhost ~]# tiup cluster deploy mytidb_cluster v6.1.1 /tidb/topology.yaml
tiup is checking updates for component cluster ...
Starting component `cluster`: /root/.tiup/components/cluster/v1.10.3/tiup-cluster deploy mytidb_cluster v6.1.1 /tidb/topology.yaml

+ Detect CPU Arch Name
  - Detecting node 192.168.200.57 Arch info ... Done

+ Detect CPU OS Name
  - Detecting node 192.168.200.57 OS info ... Done
Please confirm your topology:
Cluster type:    tidb
Cluster name:    mytidb_cluster
Cluster version: v6.1.1
Role          Host            Ports                            OS/Arch       Directories
----          ----            -----                            -------       -----------
pd            192.168.200.57  2379/2380                        linux/x86_64  /tidb-deploy/pd-2379,/tidb-data/pd-2379
tikv          192.168.200.57  20160/20180                      linux/x86_64  /tidb-deploy/tikv-20160,/tidb-data/tikv-20160
tidb          192.168.200.57  4000/10080                       linux/x86_64  /tidb-deploy/tidb-4000
tiflash       192.168.200.57  9000/8123/3930/20170/20292/8234  linux/x86_64  /tidb-deploy/tiflash-9000,/tidb-data/tiflash-9000
prometheus    192.168.200.57  9090/12020                       linux/x86_64  /tidb-deploy/prometheus-9090,/tidb-data/prometheus-9090
grafana       192.168.200.57  3000                             linux/x86_64  /tidb-deploy/grafana-3000
alertmanager  192.168.200.57  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]: (default=N) y
+ Generate SSH keys ... Done
+ Download TiDB components
  - Download pd:v6.1.1 (linux/amd64) ... Done
  - Download tikv:v6.1.1 (linux/amd64) ... Done
  - Download tidb:v6.1.1 (linux/amd64) ... Done
  - Download tiflash:v6.1.1 (linux/amd64) ... Done
  - Download prometheus:v6.1.1 (linux/amd64) ... Done
  - Download grafana:v6.1.1 (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 192.168.200.57:22 ... Done
+ Deploy TiDB instance
  - Copy pd -> 192.168.200.57 ... Done
  - Copy tikv -> 192.168.200.57 ... Done
  - Copy tidb -> 192.168.200.57 ... Done
  - Copy tiflash -> 192.168.200.57 ... Done
  - Copy prometheus -> 192.168.200.57 ... Done
  - Copy grafana -> 192.168.200.57 ... Done
  - Copy alertmanager -> 192.168.200.57 ... Done
  - Deploy node_exporter -> 192.168.200.57 ... Done
  - Deploy blackbox_exporter -> 192.168.200.57 ... Done
+ Copy certificate to remote host
+ Init instance configs
  - Generate config pd -> 192.168.200.57:2379 ... Done
  - Generate config tikv -> 192.168.200.57:20160 ... Done
  - Generate config tidb -> 192.168.200.57:4000 ... Done
  - Generate config tiflash -> 192.168.200.57:9000 ... Done
  - Generate config prometheus -> 192.168.200.57:9090 ... Done
  - Generate config grafana -> 192.168.200.57:3000 ... Done
  - Generate config alertmanager -> 192.168.200.57:9093 ... Done
+ Init monitor configs
  - Generate config node_exporter -> 192.168.200.57 ... Done
  - Generate config blackbox_exporter -> 192.168.200.57 ... Done
Enabling component pd
        Enabling instance 192.168.200.57:2379
        Enable instance 192.168.200.57:2379 success
Enabling component tikv
        Enabling instance 192.168.200.57:20160
        Enable instance 192.168.200.57:20160 success
Enabling component tidb
        Enabling instance 192.168.200.57:4000
        Enable instance 192.168.200.57:4000 success
Enabling component tiflash
        Enabling instance 192.168.200.57:9000
        Enable instance 192.168.200.57:9000 success
Enabling component prometheus
        Enabling instance 192.168.200.57:9090
        Enable instance 192.168.200.57:9090 success
Enabling component grafana
        Enabling instance 192.168.200.57:3000
        Enable instance 192.168.200.57:3000 success
Enabling component alertmanager
        Enabling instance 192.168.200.57:9093
        Enable instance 192.168.200.57:9093 success
Enabling component node_exporter
        Enabling instance 192.168.200.57
        Enable 192.168.200.57 success
Enabling component blackbox_exporter
        Enabling instance 192.168.200.57
        Enable 192.168.200.57 success
Cluster `mytidb_cluster` deployed successfully, you can start it with command: `tiup cluster start mytidb_cluster --init`

7、启动tidb：

 tiup cluster start mytidb_cluster --init

错误一(4000端口启动不成功)：

[error="context deadline exceeded"]
[stack="github.com/pingcap/tidb/session.mustExecute\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:2477\ngithub.com/pingcap/tidb/session.insertBuiltinBindInfoRow\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:1636\ngithub.com/pingcap/tidb/session.initBindInfoTable\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:1632\ngithub.com/pingcap/tidb/session.doDDLWorks\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:2287\ngithub.com/pingcap/tidb/session.bootstrap\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/bootstrap.go:527\ngithub.com/pingcap/tidb/session.runInBootstrapSession\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:3428\ngithub.com/pingcap/tidb/session.BootstrapSession\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:3264\nmain.createStoreAndDomain\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/tidb-server/main.go:318\nmain.main\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/tidb-server/main.go:218\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250"]

解决办法：磁盘空间不足，增加磁盘空间，或删除不必要的文件，释放磁盘空间。

 错误二(tiflash 9000端口启动错误)：

[root@localhost tidb]#  tiup cluster start mytidb_cluster --init
tiup is checking updates for component cluster ...
Starting component `cluster`: /root/.tiup/components/cluster/v1.10.3/tiup-cluster start mytidb_cluster --init
Starting cluster mytidb_cluster...
+ [ Serial ] - SSHKeySet: privateKey=/root/.tiup/storage/cluster/clusters/mytidb_cluster/ssh/id_rsa, publicKey=/root/.tiup/storage/cluster/clusters/mytidb_cluster/ssh/id_rsa.pub
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [ Serial ] - StartCluster
Starting component pd
        Starting instance 192.168.200.57:2379
        Start instance 192.168.200.57:2379 success
Starting component tikv
        Starting instance 192.168.200.57:20160
        Start instance 192.168.200.57:20160 success
Starting component tidb
        Starting instance 192.168.200.57:4000
        Start instance 192.168.200.57:4000 success
Starting component tiflash
        Starting instance 192.168.200.57:9000

Error: failed to start tiflash: failed to start: 192.168.200.57 tiflash-9000.service, please check the instance's log(/tidb-deploy/tiflash-9000/log) for more detail.: timed out waiting for port 9000 to be started after 2m0s

Verbose debug logs has been written to /root/.tiup/logs/tiup-cluster-debug-2023-11-01-08-53-59.log.
cat /root/.tiup/logs/tiup-cluster-debug-2023-11-01-08-53-59.lo
2023-11-01T08:53:59.723+0800    DEBUG   retry error     {"error": "operation timed out after 2m0s"}
2023-11-01T08:53:59.723+0800    DEBUG   TaskFinish      {"task": "StartCluster", "error": "failed to start tiflash: failed to start: 192.168.200.57 tiflash-9000.service, please check the instance's log(/tidb-deploy/tiflash-9000/log) for more detail.: timed out waiting for port 9000 to be started after 2m0s", "errorVerbose": "timed out waiting for port 9000 to be started after 2m0s\ngithub.com/pingcap/tiup/pkg/cluster/module.(*WaitFor).Execute\n\tgithub.com/pingcap/tiup/pkg/cluster/module/wait_for.go:91\ngithub.com/pingcap/tiup/pkg/cluster/spec.PortStarted\n\tgithub.com/pingcap/tiup/pkg/cluster/spec/instance.go:116\ngithub.com/pingcap/tiup/pkg/cluster/spec.(*TiFlashInstance).Ready\n\tgithub.com/pingcap/tiup/pkg/cluster/spec/tiflash.go:803\ngithub.com/pingcap/tiup/pkg/cluster/operation.startInstance\n\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:404\ngithub.com/pingcap/tiup/pkg/cluster/operation.StartComponent.func1\n\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:533\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.0.0-20220513210516-0976fa681c29/errgroup/errgroup.go:74\nruntime.goexit\n\truntime/asm_amd64.s:1571\nfailed to start: 192.168.200.57 tiflash-9000.service, please check the instance's log(/tidb-deploy/tiflash-9000/log) for more detail.\nfailed to start tiflash"}
2023-11-01T08:53:59.723+0800    INFO    Execute command finished        {"code": 1, "error": "failed to start tiflash: failed to start: 192.168.200.57 tiflash-9000.service, please check the instance's log(/tidb-deploy/tiflash-9000/log) for more detail.: timed out waiting for port 9000 to be started after 2m0s", "errorVerbose": "timed out waiting for port 9000 to be started after 2m0s\ngithub.com/pingcap/tiup/pkg/cluster/module.(*WaitFor).Execute\n\tgithub.com/pingcap/tiup/pkg/cluster/module/wait_for.go:91\ngithub.com/pingcap/tiup/pkg/cluster/spec.PortStarted\n\tgithub.com/pingcap/tiup/pkg/cluster/spec/instance.go:116\ngithub.com/pingcap/tiup/pkg/cluster/spec.(*TiFlashInstance).Ready\n\tgithub.com/pingcap/tiup/pkg/cluster/spec/tiflash.go:803\ngithub.com/pingcap/tiup/pkg/cluster/operation.startInstance\n\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:404\ngithub.com/pingcap/tiup/pkg/cluster/operation.StartComponent.func1\n\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:533\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.0.0-20220513210516-0976fa681c29/errgroup/errgroup.go:74\nruntime.goexit\n\truntime/asm_amd64.s:1571\nfailed to start: 192.168.200.57 tiflash-9000.service, please check the instance's log(/tidb-deploy/tiflash-9000/log) for more detail.\nfailed to start tiflash"}
root@localhost log]# cat /tidb-deploy/tiflash-9000/log/tiflash_error.log
[2023/11/01 09:48:04.625 +08:00] [ERROR] [<unknown>] ["Application:Exception: Could not determine time zone from TZ variable value: '/etc/localtime': custom time zone file used."] [thread_id=1]
[2023/11/01 09:48:20.123 +08:00] [ERROR] [<unknown>] ["Application:Exception: Could not determine time zone from TZ variable value: '/etc/localtime': custom time zone file used."] [thread_id=1]
[2023/11/01 09:48:35.621 +08:00] [ERROR] [<unknown>] ["Application:Exception: Could not determine time zone from TZ variable value: '/etc/localtime': custom time zone file used."] [thread_id=1]
[2023/11/01 09:48:51.120 +08:00] [ERROR] [<unknown>] ["Application:Exception: Could not determine time zone from TZ variable value: '/etc/localtime': custom time zone file used."] [thread_id=1]
[2023/11/01 09:49:06.623 +08:00] [ERROR] [<unknown>] ["Application:Exception: Could not determine time zone from TZ variable value: '/etc/localtime': custom time zone file used."] [thread_id=1]
[2023/11/01 09:49:22.128 +08:00] [ERROR] [<unknown>] ["Application:Exception: Could not determine time zone from TZ variable value: '/etc/localtime': custom time zone file used."] [thread_id=1]

解决办法：（时区问题造成的）

cp /usr/share/zoneinfo/Asia/Shanghai /etc/localtime

错误三(blackbox_exporter-9115.service启动失败)：

[root@localhost log]#  tiup cluster start mytidb_cluster --init
tiup is checking updates for component cluster ...
Starting component `cluster`: /root/.tiup/components/cluster/v1.10.3/tiup-cluster start mytidb_cluster --init
Starting cluster mytidb_cluster...
+ [ Serial ] - SSHKeySet: privateKey=/root/.tiup/storage/cluster/clusters/mytidb_cluster/ssh/id_rsa, publicKey=/root/.tiup/storage/cluster/clusters/mytidb_cluster/ssh/id_rsa.pub
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [ Serial ] - StartCluster
Starting component pd
        Starting instance 192.168.200.57:2379
        Start instance 192.168.200.57:2379 success
Starting component tikv
        Starting instance 192.168.200.57:20160
        Start instance 192.168.200.57:20160 success
Starting component tidb
        Starting instance 192.168.200.57:4000
        Start instance 192.168.200.57:4000 success
Starting component tiflash
        Starting instance 192.168.200.57:9000
        Start instance 192.168.200.57:9000 success
Starting component prometheus
        Starting instance 192.168.200.57:9090
        Start instance 192.168.200.57:9090 success
Starting component grafana
        Starting instance 192.168.200.57:3000
        Start instance 192.168.200.57:3000 success
Starting component alertmanager
        Starting instance 192.168.200.57:9093
        Start instance 192.168.200.57:9093 success
Starting component node_exporter
        Starting instance 192.168.200.57
        Start 192.168.200.57 success
Starting component blackbox_exporter
        Starting instance 192.168.200.57

Error: failed to start: 192.168.200.57 blackbox_exporter-9115.service, please check the instance's log() for more detail.: timed out waiting for port 9115 to be started after 2m0s
[root@localhost log]#cat /root/.tiup/logs/tiup-cluster-debug-2023-11-01-09-53-02.log
2023-11-01T09:53:02.262+0800    DEBUG   retry error     {"error": "operation timed out after 2m0s"}
2023-11-01T09:53:02.262+0800    DEBUG   TaskFinish      {"task": "StartCluster", "error": "failed to start: 192.168.200.57 blackbox_exporter-9115.service, please check the instance's log() for more detail.: timed out waiting for port 9115 to be started after 2m0s", "errorVerbose": "timed out waiting for port 9115 to be started after 2m0s\ngithub.com/pingcap/tiup/pkg/cluster/module.(*WaitFor).Execute\n\tgithub.com/pingcap/tiup/pkg/cluster/module/wait_for.go:91\ngithub.com/pingcap/tiup/pkg/cluster/spec.PortStarted\n\tgithub.com/pingcap/tiup/pkg/cluster/spec/instance.go:116\ngithub.com/pingcap/tiup/pkg/cluster/operation.systemctlMonitor.func1\n\tgithub.com/pingcap/tiup/pkg/cluster/operation/action.go:335\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.0.0-20220513210516-0976fa681c29/errgroup/errgroup.go:74\nruntime.goexit\n\truntime/asm_amd64.s:1571\nfailed to start: 192.168.200.57 blackbox_exporter-9115.service, please check the instance's log()for more detail."}

解决办法：

将/etc/systemd/system/multi-user.target.wants/blackbox_exporter-9115.service文件中的AmbientCapabilities=CAP_NET_RAW注释掉。

正确结果：

[root@localhost log]#  tiup cluster start mytidb_cluster --init
tiup is checking updates for component cluster ...
Starting component `cluster`: /root/.tiup/components/cluster/v1.10.3/tiup-cluster start mytidb_cluster --init
Starting cluster mytidb_cluster...
+ [ Serial ] - SSHKeySet: privateKey=/root/.tiup/storage/cluster/clusters/mytidb_cluster/ssh/id_rsa, publicKey=/root/.tiup/storage/cluster/clusters/mytidb_cluster/ssh/id_rsa.pub
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [Parallel] - UserSSH: user=tidb, host=192.168.200.57
+ [ Serial ] - StartCluster
Starting component pd
        Starting instance 192.168.200.57:2379
        Start instance 192.168.200.57:2379 success
Starting component tikv
        Starting instance 192.168.200.57:20160
        Start instance 192.168.200.57:20160 success
Starting component tidb
        Starting instance 192.168.200.57:4000
        Start instance 192.168.200.57:4000 success
Starting component tiflash
        Starting instance 192.168.200.57:9000
        Start instance 192.168.200.57:9000 success
Starting component prometheus
        Starting instance 192.168.200.57:9090
        Start instance 192.168.200.57:9090 success
Starting component grafana
        Starting instance 192.168.200.57:3000
        Start instance 192.168.200.57:3000 success
Starting component alertmanager
        Starting instance 192.168.200.57:9093
        Start instance 192.168.200.57:9093 success
Starting component node_exporter
        Starting instance 192.168.200.57
        Start 192.168.200.57 success
Starting component blackbox_exporter
        Starting instance 192.168.200.57
        Start 192.168.200.57 success
+ [ Serial ] - UpdateTopology: cluster=mytidb_cluster
Started cluster `mytidb_cluster` successfully
The root password of TiDB database has been changed.
The new password is: 'BZ$6K587Yt4+C!3z@T'.
Copy and record it to somewhere safe, it is only displayed once, and will not be stored.
The generated password can NOT be get and shown again.

8、登录数据库修改初始密码：

/mysqlsoft/mysql/bin/mysql -h 192.168.200.57 -P4000 -uroot -p#之后输入启动成功后生成的临时密码。即可进入数据库

修改数据库密码，刷新权限： 

set password for 'root'@'%' = 'tidb';
flush privileges;
[root@localhost log]# /mysqlsoft/mysql/bin/mysql -h 192.168.200.57 -P4000 -uroot -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 407
Server version: 5.7.25-TiDB-v6.1.1 TiDB Server (Apache License 2.0) Community Edition, MySQL 5.7 compatible

Copyright (c) 2000, 2019, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> set password for 'root'@'%' = 'tidb';
Query OK, 0 rows affected (0.04 sec)

mysql> flush privileges;
Query OK, 0 rows affected (0.05 sec)

mysql>

 9、卸载tidb步骤：

停止
tiup cluster stop mytidb_cluster
清理数据
tiup cluster clean mytidb_cluster --all
卸载
tiup cluster destroy mytidb_cluster

huangsu_123
关注
Tidb实战部署[单节点部署][集群部署][Ansible集群部署]
weixin_44480386的博客
08-05 1073
TIDB简介 TiDB 是 PingCAP 公司设计的开源分布式 HTAP (Hybrid Transactional and Analytical Processing) 数据库，结合了传统的 RDBMS 和 NoSQL 的最佳特性。TiDB 兼容 MySQL，支持无限的水平扩展，具备强一致性和高可用性。TiDB 的目标是为 OLTP (Online Transactional Processing) 和 OLAP (Online Analytical Processing) 场景提供一站式的解决方案。
TiDB安装
热门推荐
小伟的博客
03-29 1万+
官方地址： https://github.com/pingcap/docs-cn1.下载压缩包wget http://download.pingcap.org/tidb-latest-linux-amd64.tar.gzwget http://download.pingcap.org/tidb-latest-linux-amd64.sha2562.检查文件完整性[root@localhost to...
TiDB集群安装(TiUP方式)-保姆级教程
八月林城的博客
06-12 3893
tidb集群安装教程
TiDB部署搭建（Linux）
CSDN博客技术，java高级工程师，业务层架构师，高级管理认证，毕业设计可以联系我
01-25 617
上述命令会在本地下载并启动某个版本的集群（例如 v5.0.2），–monitor 表示同时部署监控组件。最新版本可以通过执行 tiup list tidb 来查看。运行结果将显示集群的访问方式。mysql链接 mysql --host 127.0.0.1 --port 4000 -u root。
TiDB的环境（linux）部署与安装
Redmonster0923的博客
11-15 2183
TiDB快速上手指南 首先我们需要准备一台Linux虚拟机，配置好网络环境，并且关闭防火墙 网卡配置 关闭防火墙 CentOS默认安装防火墙位置firewall 查看防火墙状态 systemctl status firewall.service 关闭防火墙 systemctl stop firewall.service 永久关闭防火墙 systemctldisablefirewall.service 恢复防火墙随系统而启动 systemctl enablefi...
linux中安装tidb单机版本
王林冲的博客
10-21 2349
安装tidb数据库 在opt下新建一个tidb文件夹： cd /opt/ mkdir tidb cd tidb 1.下载压缩包 安装tar包路径 命令：wget http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz 命令：wget http://download.pingcap.org/tidb-latest-linux-amd64.sha256 2.检查文件完整性 命令：sha256sum -c tidb...
TiDB单节点部署
shy_snow的专栏
03-10 1005
wget http://download.pingcap.org/tidb-latest-linux-amd64.tar.gz wget http://download.pingcap.org/tidb-latest-linux-amd64.sha256 sha256sum -c tidb-latest-linux-amd64.sha256 tar -xzf tidb-latest-linux-amd64.tar.gz #根据解压实际的版本进入目录 cd tidb-v5.0.1-linux-amd
TiDB单机模拟集群快速上手
小小白的博客
08-30 193
单机部署模拟集群环境
tidb安装详细步骤 单机安装 集群安装
02-22
TiDB（TiKV分布式数据库）是一款开源的、分布式的NewSQL数据库，设计灵感来源于Google的Spanner和F1，主要用于处理大规模并发事务和分析查询。它支持MySQL协议，可以无缝对接MySQL应用，同时具备水平扩展和强一致性...
tidb离线单机单节点部署
最新发布
02-18
### TiDB 离线单机单节点部署方法 #### 准备工作 为了成功完成 TiDB 的离线单机单节点部署，需准备如下材料： - 对应版本的 TiDB Server 离线镜像包，该包内含 TiUP 离线组件[^1]。 - 下载 `TiDB-community-...
TiDB v7.5.0单机离线部署
linnana的专栏
01-10 1868
TiDB 7.5.0关键特性： 支持并行运行多个 ADD INDEX 语句 优化全局排序（实验特性，从 v7.4.0 开始引入） 资源管控支持自动管理后台任务（实验特性，从 v7.4.0 开始引入） 资源管控支持管理资源消耗超出预期的查询（实验特性，从 v7.2.0 开始引入） TiDB 支持完整的分区类型管理功能 MySQL 8.0 兼容性（从 v7.4.0 开始引入） IMPORT INTO 语句集成 TiDB Lightning 物理导入模式的能力 (GA) ...
在Linux环境下部署TiDB可以通过几种不同的方法
m0_58223765的博客
11-14 800
在Linux环境下部署TiDB可以通过几种不同的方法，包括使用TiDB官方提供的二进制包、Docker容器、Kubernetes等。最常见的方法是使用TiDB官方的二进制包，下面将详细介绍如何在Linux系统上手动部署TiDB。
单节点离线部署TiDB 6.1用于测试
zxrhhm的博客
06-07 913
单节点离线部署TiDB 6.1用于测试兼容MySQL特性
TIDB-在单机上模拟部署生产环境集群（支持 Linux）
hxspringriver的专栏
07-25 701
tidb 8.2 单机安装体验
TiDB单机部署
互联网知识分享
07-26 1103
数据库，具有强一致性、高可用性和水平扩展性的特性。它可以在多台机器上部署，并提供支持分布式事务和透明的数据复制的功能。的简单示例代码和参数介绍。查询接口和逻辑计划生成，将查询连接到底层存储引擎。：作为底层存储引擎，提供数据持久化和查询功能。：提供分布式存储能力，负责存储和处理数据。在以上示例代码中，我们使用了一些参数来配置。来存储和管理集群元数据，我们先安装并配置。，以及相关的原理和代码示例。创建一个新的数据库用户和密码。完成后，我们可以安装和配置。：创建一个新的数据库用户。最后，我们安装和配置。
tidb安装
superaaa的专栏
01-17 432
   68  ./bin/pd-server --data-dir=pd    69  ./bin/tikv-server --pd="127.0.0.1:2379"                   --store=tikv    70  ./bin/tikv-server --pd="127.0.0.1:2379" --store=tikv    81  ./bin/tikv-server ...
TiDB安装部署
colin726的博客
03-09 531
TiDB安装部署
TiDB 单节点部署
firetaker的专栏
06-21 2782
tidb single node devops howto
Linux Ubuntu安装Tidb
Hi文的博客
03-02 2078
部署本地测试集群 适用场景：利用本地单机 Linux 环境快速部署 TiDB 测试集群，体验 TiDB 集群的基本架构，以及 TiDB、TiKV、PD、监控等基础组件的运行。 1.下载并安装 TiUP ~$ curl --proto '=https' --tlsv1.2 -sSf https://tiup-mirrors.pingcap.com/install.sh | sh 2.声明全局环境变量 注意 TiUP 安装完成后会提示对应 profile 文件的绝对路径。在执行以下 source 命令前
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值