[转帖]tidb4.0.4使用tiup扩容TiKV 节点

https://blog.csdn.net/mchdba/article/details/108896766

环境：centos7、tidb4.0.4、tiup-v1.0.8

添加两个tikv节点 172.21.210.37-38

思路：初始化两台服务器、配置ssh互通——>编辑配置文件——>执行扩容命令——>重启grafana

1、初始化服务器、配置ssh互通

1、时间同步

2、配置ssh

ssh-copy-id root@172.21.210.37

ssh-copy-id root@172.21.210.38

2、编辑配置文件

tiup cluster list                                     #查看当前的集群名称列表

tiup cluster edit-config <cluster-name> #查看集群配置、拷贝对应的配置

vi scale-out.yaml

tikv_servers:

- host: 172.21.210.37

ssh_port: 22

port: 20160

status_port: 20180

deploy_dir: /data1/tidb-deploy/tikv-20160

data_dir: /data1/tidb-data/tikv-20160

arch: amd64

os: linux

- host: 172.21.210.38

ssh_port: 22

port: 20160

status_port: 20180

deploy_dir: /data1/tidb-deploy/tikv-20160

data_dir: /data1/tidb-data/tikv-20160

arch: amd64

os: linux

3、执行扩容命令

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

此处假设当前执行命令的用户和新增的机器打通了互信，如果不满足已打通互信的条件，需要通过 -p 来输入新机器的密码，或通过 -i 指定私钥文件。

tiup cluster scale-out <cluster-name> scale-out.yaml

预期输出 Scaled cluster <cluster-name> out successfully 信息，表示扩容操作成功

root@host-172-21-210-32 tidb_config]# tiup cluster scale-out tidb scale-out.yaml

Starting component `cluster`: scale-out tidb scale-out.yaml

Please confirm your topology:

TiDB Cluster: tidb

TiDB Version: v4.0.4

Type Host Ports OS/Arch Directories

---- ---- ----- ------- -----------

tikv 172.21.210.37 20160/20180 linux/x86_64 /data1/tidb-deploy/tikv-20160,/data1/tidb-data/tikv-20160

tikv 172.21.210.38 20160/20180 linux/x86_64 /data1/tidb-deploy/tikv-20160,/data1/tidb-data/tikv-20160

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

+ [ Serial ] - SSHKeySet: privateKey=/root/.tiup/storage/cluster/clusters/tidb/ssh/id_rsa, publicKey=/root/.tiup/storage/cluster/clusters/tidb/ssh/id_rsa.pub

- Download tikv:v4.0.4 (linux/amd64) ... Done

+ [ Serial ] - RootSSH: user=root, host=172.21.210.38, port=22, key=/root/.ssh/id_rsa

+ [ Serial ] - EnvInit: user=tidb, host=172.21.210.38

+ [ Serial ] - RootSSH: user=root, host=172.21.210.37, port=22, key=/root/.ssh/id_rsa

+ [ Serial ] - EnvInit: user=tidb, host=172.21.210.37

+ [ Serial ] - Mkdir: host=172.21.210.37, directories='/data1/tidb-deploy','/data1/tidb-data'

+ [ Serial ] - Mkdir: host=172.21.210.38, directories='/data1/tidb-deploy','/data1/tidb-data'

+ [Parallel] - UserSSH: user=tidb, host=172.21.210.32

+ [Parallel] - UserSSH: user=tidb, host=172.21.210.39

+ [Parallel] - UserSSH: user=tidb, host=172.21.210.33

+ [Parallel] - UserSSH: user=tidb, host=172.21.210.34

+ [Parallel] - UserSSH: user=tidb, host=172.21.210.32

+ [Parallel] - UserSSH: user=tidb, host=172.21.210.33

+ [Parallel] - UserSSH: user=tidb, host=172.21.210.35

+ [Parallel] - UserSSH: user=tidb, host=172.21.210.32

+ [Parallel] - UserSSH: user=tidb, host=172.21.210.36

+ [Parallel] - UserSSH: user=tidb, host=172.21.210.32

+ [ Serial ] - UserSSH: user=tidb, host=172.21.210.38

+ [ Serial ] - UserSSH: user=tidb, host=172.21.210.37

+ [ Serial ] - Mkdir: host=172.21.210.38, directories='/data1/tidb-deploy/tikv-20160','/data1/tidb-deploy/tikv-20160/log','/data1/tidb-deploy/tikv-20160/bin','/data1/tidb-deploy/tikv-20160/conf','/data1/tidb-deploy/tikv-20160/scripts'

+ [ Serial ] - Mkdir: host=172.21.210.37, directories='/data1/tidb-deploy/tikv-20160','/data1/tidb-deploy/tikv-20160/log','/data1/tidb-deploy/tikv-20160/bin','/data1/tidb-deploy/tikv-20160/conf','/data1/tidb-deploy/tikv-20160/scripts'

- Copy blackbox_exporter -> 172.21.210.37 ... ? Mkdir: host=172.21.210.37, directories='/data1/tidb-deploy/monitor-9100','/data1/t...

- Copy node_exporter -> 172.21.210.37 ... ? CopyComponent: component=node_exporter, version=v0.17.0, remote=172.21.210.37:/data1/t...

- Copy blackbox_exporter -> 172.21.210.37 ... ? MonitoredConfig: cluster=tidb, user=tidb, node_exporter_port=9100, blackbox_export...

- Copy node_exporter -> 172.21.210.38 ... Done

+ [ Serial ] - ScaleConfig: cluster=tidb, user=tidb, host=172.21.210.37, service=tikv-20160.service, deploy_dir=/data1/tidb-deploy/tikv-20160, data_dir=[/data1/tidb-data/tikv-20160], log_dir=/data1/tidb-deploy/tikv-20160/log, cache_dir=

+ [ Serial ] - ScaleConfig: cluster=tidb, user=tidb, host=172.21.210.38, service=tikv-20160.service, deploy_dir=/data1/tidb-deploy/tikv-20160, data_dir=[/data1/tidb-data/tikv-20160], log_dir=/data1/tidb-deploy/tikv-20160/log, cache_dir=

+ [ Serial ] - ClusterOperate: operation=StartOperation, options={Roles:[] Nodes:[] Force:false SSHTimeout:0 OptTimeout:120 APITimeout:0 IgnoreConfigCheck:false RetainDataRoles:[] RetainDataNodes:[]}

Starting component pd

Starting instance pd 172.21.210.33:2379

Starting instance pd 172.21.210.32:2379

Start pd 172.21.210.33:2379 success

Start pd 172.21.210.32:2379 success

Starting component node_exporter

Starting instance 172.21.210.32

Start 172.21.210.32 success

Starting component blackbox_exporter

Starting instance 172.21.210.32

Start 172.21.210.32 success

Starting component node_exporter

Starting instance 172.21.210.33

Start 172.21.210.33 success

Starting component blackbox_exporter

Starting instance 172.21.210.33

Start 172.21.210.33 success

Starting component tikv

Starting instance tikv 172.21.210.35:20160

Starting instance tikv 172.21.210.34:20160

Starting instance tikv 172.21.210.39:20160

Starting instance tikv 172.21.210.36:20160

Start tikv 172.21.210.39:20160 success

Start tikv 172.21.210.34:20160 success

Start tikv 172.21.210.35:20160 success

Start tikv 172.21.210.36:20160 success

Starting component node_exporter

Starting instance 172.21.210.35

Start 172.21.210.35 success

Starting component blackbox_exporter

Starting instance 172.21.210.35

Start 172.21.210.35 success

Starting component node_exporter

Starting instance 172.21.210.34

Start 172.21.210.34 success

Starting component blackbox_exporter

Starting instance 172.21.210.34

Start 172.21.210.34 success

Starting component node_exporter

Starting instance 172.21.210.39

Start 172.21.210.39 success

Starting component blackbox_exporter

Starting instance 172.21.210.39

Start 172.21.210.39 success

Starting component node_exporter

Starting instance 172.21.210.36

Start 172.21.210.36 success

Starting component blackbox_exporter

Starting instance 172.21.210.36

Start 172.21.210.36 success

Starting component tidb

Starting instance tidb 172.21.210.33:4000

Starting instance tidb 172.21.210.32:4000

Start tidb 172.21.210.32:4000 success

Start tidb 172.21.210.33:4000 success

Starting component prometheus

Starting instance prometheus 172.21.210.32:9090

Start prometheus 172.21.210.32:9090 success

Starting component grafana

Starting instance grafana 172.21.210.32:3000

Start grafana 172.21.210.32:3000 success

Starting component alertmanager

Starting instance alertmanager 172.21.210.32:9093

Start alertmanager 172.21.210.32:9093 success

Checking service state of pd

172.21.210.32 Active: active (running) since Fri 2020-10-16 22:50:31 CST; 2 weeks 5 days ago

172.21.210.33 Active: active (running) since Fri 2020-10-16 22:50:22 CST; 2 weeks 5 days ago

Checking service state of tikv

172.21.210.34 Active: active (running) since Fri 2020-10-16 22:50:19 CST; 2 weeks 5 days ago

172.21.210.35 Active: active (running) since Fri 2020-10-16 22:50:19 CST; 2 weeks 5 days ago

172.21.210.36 Active: active (running) since Sat 2020-10-17 02:25:23 CST; 2 weeks 5 days ago

172.21.210.39 Active: active (running) since Fri 2020-10-16 23:34:13 CST; 2 weeks 5 days ago

Checking service state of tidb

172.21.210.32 Active: active (running) since Fri 2020-10-16 22:50:49 CST; 2 weeks 5 days ago

172.21.210.33 Active: active (running) since Fri 2020-10-16 22:50:40 CST; 2 weeks 5 days ago

Checking service state of prometheus

172.21.210.32 Active: active (running) since Sat 2020-10-17 02:25:27 CST; 2 weeks 5 days ago

Checking service state of grafana

172.21.210.32 Active: active (running) since Fri 2020-10-16 23:55:07 CST; 2 weeks 5 days ago

Checking service state of alertmanager

172.21.210.32 Active: active (running) since Fri 2020-10-16 22:51:06 CST; 2 weeks 5 days ago

+ [Parallel] - UserSSH: user=tidb, host=172.21.210.38

+ [Parallel] - UserSSH: user=tidb, host=172.21.210.37

+ [ Serial ] - save meta

Starting component tikv

Starting instance tikv 172.21.210.38:20160

Starting instance tikv 172.21.210.37:20160

Start tikv 172.21.210.37:20160 success

Start tikv 172.21.210.38:20160 success

Starting component node_exporter

Starting instance 172.21.210.37

Start 172.21.210.37 success

Starting component blackbox_exporter

Starting instance 172.21.210.37

Start 172.21.210.37 success

Starting component node_exporter

Starting instance 172.21.210.38

Start 172.21.210.38 success

Starting component blackbox_exporter

Starting instance 172.21.210.38

Start 172.21.210.38 success

Checking service state of tikv

172.21.210.37 Active: active (running) since Thu 2020-11-05 11:33:46 CST; 3s ago

172.21.210.38 Active: active (running) since Thu 2020-11-05 11:33:46 CST; 2s ago

+ [ Serial ] - InitConfig: cluster=tidb, user=tidb, host=172.21.210.32, path=/root/.tiup/storage/cluster/clusters/tidb/config-cache/alertmanager-9093.service, deploy_dir=/data1/tidb-deploy/alertmanager-9093, data_dir=[/data1/tidb-data/alertmanager-9093], log_dir=/data1/tidb-deploy/alertmanager-9093/log, cache_dir=/root/.tiup/storage/cluster/clusters/tidb/config-cache

+ [ Serial ] - InitConfig: cluster=tidb, user=tidb, host=172.21.210.36, path=/root/.tiup/storage/cluster/clusters/tidb/config-cache/tikv-20160.service, deploy_dir=/data1/tidb-deploy/tikv-20160, data_dir=[/data1/tidb-data/tikv-20160], log_dir=/data1/tidb-deploy/tikv-20160/log, cache_dir=/root/.tiup/storage/cluster/clusters/tidb/config-cache

+ [ Serial ] - InitConfig: cluster=tidb, user=tidb, host=172.21.210.32, path=/root/.tiup/storage/cluster/clusters/tidb/config-cache/tidb-4000.service, deploy_dir=/data1/tidb-deploy/tidb-4000, data_dir=[], log_dir=/data1/tidb-deploy/tidb-4000/log, cache_dir=/root/.tiup/storage/cluster/clusters/tidb/config-cache

+ [ Serial ] - InitConfig: cluster=tidb, user=tidb, host=172.21.210.32, path=/root/.tiup/storage/cluster/clusters/tidb/config-cache/pd-2379.service, deploy_dir=/data1/tidb-deploy/pd-2379, data_dir=[/data1/tidb-data/pd-2379], log_dir=/data1/tidb-deploy/pd-2379/log, cache_dir=/root/.tiup/storage/cluster/clusters/tidb/config-cache

+ [ Serial ] - InitConfig: cluster=tidb, user=tidb, host=172.21.210.37, path=/root/.tiup/storage/cluster/clusters/tidb/config-cache/tikv-20160.service, deploy_dir=/data1/tidb-deploy/tikv-20160, data_dir=[/data1/tidb-data/tikv-20160], log_dir=/data1/tidb-deploy/tikv-20160/log, cache_dir=/root/.tiup/storage/cluster/clusters/tidb/config-cache

+ [ Serial ] - InitConfig: cluster=tidb, user=tidb, host=172.21.210.33, path=/root/.tiup/storage/cluster/clusters/tidb/config-cache/tidb-4000.service, deploy_dir=/data1/tidb-deploy/tidb-4000, data_dir=[], log_dir=/data1/tidb-deploy/tidb-4000/log, cache_dir=/root/.tiup/storage/cluster/clusters/tidb/config-cache

+ [ Serial ] - InitConfig: cluster=tidb, user=tidb, host=172.21.210.35, path=/root/.tiup/storage/cluster/clusters/tidb/config-cache/tikv-20160.service, deploy_dir=/data1/tidb-deploy/tikv-20160, data_dir=[/data1/tidb-data/tikv-20160], log_dir=/data1/tidb-deploy/tikv-20160/log, cache_dir=/root/.tiup/storage/cluster/clusters/tidb/config-cache

+ [ Serial ] - InitConfig: cluster=tidb, user=tidb, host=172.21.210.32, path=/root/.tiup/storage/cluster/clusters/tidb/config-cache/prometheus-9090.service, deploy_dir=/data1/tidb-deploy/prometheus-9090, data_dir=[/data1/tidb-data/prometheus-9090], log_dir=/data1/tidb-deploy/prometheus-9090/log, cache_dir=/root/.tiup/storage/cluster/clusters/tidb/config-cache

+ [ Serial ] - InitConfig: cluster=tidb, user=tidb, host=172.21.210.34, path=/root/.tiup/storage/cluster/clusters/tidb/config-cache/tikv-20160.service, deploy_dir=/data1/tidb-deploy/tikv-20160, data_dir=[/data1/tidb-data/tikv-20160], log_dir=/data1/tidb-deploy/tikv-20160/log, cache_dir=/root/.tiup/storage/cluster/clusters/tidb/config-cache

+ [ Serial ] - InitConfig: cluster=tidb, user=tidb, host=172.21.210.32, path=/root/.tiup/storage/cluster/clusters/tidb/config-cache/grafana-3000.service, deploy_dir=/data1/tidb-deploy/grafana-3000, data_dir=[], log_dir=/data1/tidb-deploy/grafana-3000/log, cache_dir=/root/.tiup/storage/cluster/clusters/tidb/config-cache

+ [ Serial ] - InitConfig: cluster=tidb, user=tidb, host=172.21.210.38, path=/root/.tiup/storage/cluster/clusters/tidb/config-cache/tikv-20160.service, deploy_dir=/data1/tidb-deploy/tikv-20160, data_dir=[/data1/tidb-data/tikv-20160], log_dir=/data1/tidb-deploy/tikv-20160/log, cache_dir=/root/.tiup/storage/cluster/clusters/tidb/config-cache

+ [ Serial ] - InitConfig: cluster=tidb, user=tidb, host=172.21.210.33, path=/root/.tiup/storage/cluster/clusters/tidb/config-cache/pd-2379.service, deploy_dir=/data1/tidb-deploy/pd-2379, data_dir=[/data1/tidb-data/pd-2379], log_dir=/data1/tidb-deploy/pd-2379/log, cache_dir=/root/.tiup/storage/cluster/clusters/tidb/config-cache

+ [ Serial ] - InitConfig: cluster=tidb, user=tidb, host=172.21.210.39, path=/root/.tiup/storage/cluster/clusters/tidb/config-cache/tikv-20160.service, deploy_dir=/data1/tidb-deploy/tikv-20160, data_dir=[/data1/tidb-data/tikv-20160], log_dir=/data1/tidb-deploy/tikv-20160/log, cache_dir=/root/.tiup/storage/cluster/clusters/tidb/config-cache

+ [ Serial ] - ClusterOperate: operation=RestartOperation, options={Roles:[prometheus] Nodes:[] Force:false SSHTimeout:0 OptTimeout:120 APITimeout:0 IgnoreConfigCheck:false RetainDataRoles:[] RetainDataNodes:[]}

Stopping component prometheus

Stopping instance 172.21.210.32

Stop prometheus 172.21.210.32:9090 success

Starting component prometheus

Starting instance prometheus 172.21.210.32:9090

Start prometheus 172.21.210.32:9090 success

Starting component node_exporter

Starting instance 172.21.210.32

Start 172.21.210.32 success

Starting component blackbox_exporter

Starting instance 172.21.210.32

Start 172.21.210.32 success

Checking service state of pd

172.21.210.33 Active: active (running) since Fri 2020-10-16 22:50:22 CST; 2 weeks 5 days ago

172.21.210.32 Active: active (running) since Fri 2020-10-16 22:50:31 CST; 2 weeks 5 days ago

Checking service state of tikv

172.21.210.35 Active: active (running) since Fri 2020-10-16 22:50:19 CST; 2 weeks 5 days ago

172.21.210.39 Active: active (running) since Fri 2020-10-16 23:34:13 CST; 2 weeks 5 days ago

172.21.210.34 Active: active (running) since Fri 2020-10-16 22:50:19 CST; 2 weeks 5 days ago

172.21.210.36 Active: active (running) since Sat 2020-10-17 02:25:23 CST; 2 weeks 5 days ago

Checking service state of tidb

172.21.210.32 Active: active (running) since Fri 2020-10-16 22:50:49 CST; 2 weeks 5 days ago

172.21.210.33 Active: active (running) since Fri 2020-10-16 22:50:40 CST; 2 weeks 5 days ago

Checking service state of prometheus

172.21.210.32 Active: active (running) since Thu 2020-11-05 11:33:53 CST; 2s ago

Checking service state of grafana

172.21.210.32 Active: active (running) since Fri 2020-10-16 23:55:07 CST; 2 weeks 5 days ago

Checking service state of alertmanager

172.21.210.32 Active: active (running) since Fri 2020-10-16 22:51:06 CST; 2 weeks 5 days ago

+ [ Serial ] - UpdateTopology: cluster=tidb

Scaled cluster `tidb` out successfully

4、查看集群状态、重启grafana

检查集群状态

tiup cluster display <cluster-name>

重启grafana

tiup cluster restart tidb -R grafana

[转帖]tidb4.0.4使用tiup扩容TiKV 节点的更多相关文章

Tidb进行缩减扩容tikv节点
这两天接到任务说是要进行测试缩减机器给集群带来的负面效果有哪些. 然后我就按照官方的教程将机器进行了缩减,主要是缩减tikv节点我们先来看看官方的文章是怎么写的: 步骤都没有什么问题,就是进行到第二 ...
[转帖]springboot2.0配置连接池（hikari、druid）
springboot2.0配置连接池(hikari.druid) 原文链接:https://www.cnblogs.com/blog5277/p/10660689.html 原文作者:博客园--曲高终 ...
[转帖]从0开始的高并发（一）--- Zookeeper的基础概念
从0开始的高并发(一)--- Zookeeper的基础概念 https://juejin.im/post/5d0bd358e51d45105e0212db 前言前面几篇以spring作为主题也是有些 ...
[转帖]mysql8.0忘记密码如何操作？
mysql8.0忘记密码如何操作? https://www.cnblogs.com/gspsuccess/p/11245314.html mark 一下上次竟然不知道怎么弄. 很不幸,刚安装了MYS ...
zookeeper集群扩容/下线节点实践
环境:zookeeper版本 3.4.6jdk版本 1.7.0_8010.111.1.29 zk110.111.1.44 zk210.111.1.45 zk310.111.1.46 zk410.111 ...
MongoDB 3.0.6的主,从,仲裁节点搭建
在MongoDB所在路径创建log和data目录mkdir logmkdir data 在data目录下创建master.slaver.arbiter路径 mkdir master mkdir sl ...
【转】Rancher 2.0 里程碑版本：支持添加自定义节点！
原文链接: http://mp.weixin.qq.com/s?__biz=MzIyMTUwMDMyOQ==&mid=2247487533&idx=1&sn=c70258577 ...
11.2.0.3 RAC（VCS）节点crash以及hang的问题分析
昨天某个客户的一套双节RAC当中一个节点crash,同一时候最后导致另外一个节点也hang住,仅仅能shutdown abort. 且出现shutdown abort实例之后,还有部分进程无法通过ki ...
Hadoop 动态扩容增加节点
基础准备在基础准备部分,主要是设置hadoop运行的系统环境修改系统hostname(通过hostname和/etc/sysconfig/network进行修改) 修改hosts文件,将集群所有节 ...
在线tidb+tipd+tikv扩容，迁移，从UC到阿里云
集群现状: 共有五个节点,配置为16核32g内存,数据节点为1T ssd盘,非数据节点为100g ssd盘: 角色规划: node1 tidb tipd node2 tidb tipd node3 t ...

随机推荐

Java开发手册精华总结
阿里 Java 开发手册的思考总结一个优秀的工程师和一个普通的工程师的区别,不是满天飞的架构图,他的功底体现在所写的每一行代码上. -- 毕玄 1. 命名风格 [书摘]类名用 UpperCamelC ...
面试官：说一下Jena推理
摘要:本文介绍了Jena的推理子系统,并构建了一个简单的RDF图.基于该RDF图,我们搭建了一个Jena推理引擎,并进行自动化推理. 本文分享自华为云社区<知识推理之基于jena的知识推理(三) ...
揭秘字节跳动云原生Spark History 服务 UIService
本文是字节跳动数据平台数据引擎SparkSQL团队针对 Spark History Server (SHS) 的优化实践分享. 文 | 字节跳动数据平台-数据引擎-SparkSQL团队在字节跳动内部 ...
补齐OLAP引擎短板！ByteHouse 是如何实现流批一体的？
更多技术交流.求职机会,欢迎关注字节跳动数据平台微信公众号,回复[1]进入官方交流群计算机领域一直流传一句话--"没有银弹",这句话出自计算机科学家布鲁克斯<没有银弹& ...
Mysql--between
between 用于where 表达式中,选取介于两个值之间的数据范围,同and一起搭配使用语法: expr [NOT] BETWEEN begin_expr AND end_expr; 在整个表达 ...
【JAVA基础】事务管理
@Transactional 注解的属性介绍 @Transactional(propagation = Propagation.REQUIRED, rollbackFor = Exception.cl ...
用 three.js 绘制三维带箭头线
需求:这个需求是个刚需啊!在一个地铁场景里展示逃生路线,这个路线肯定是要有指示箭头的,为了画这个箭头,我花了不少于十几个小时,总算做出来了,但始终有点问题.我对这个箭头的要求是,无论场景拉近还是拉远, ...
关于 Windows10升级版本后，内存占用率居高不下的解决办法
一个月前,打开系统更新,win 10 推送了最新版本. 然后手贱点了更新. 的确一开始没觉得的有什么明显变化,但最近总觉得机子卡的卡的严重,查看了下内存,占用率居高不下. 经常才打开一两个软件内存就 ...
深入剖析 RSA 密钥原理及实践
一.前言在经历了人生的很多至暗时刻后,你读到了这篇文章,你会后悔甚至愤怒:为什么你没有早点写出这篇文章?! 你的至暗时刻包括: 1.你所在的项目需要对接银行,对方需要你提供一个加密证书.你手上只有一 ...
使用 Serverless Devs 插件快速部署前端应用
作者| 邓超 Serverless Devs 开源贡献者背景我们在上文 [Aliyun] [FC] 如何使用 @serverless-devs/s 部署静态网站到函数计算中,详细的介绍了如何通 ...

[转帖]tidb4.0.4使用tiup扩容TiKV 节点

[转帖]tidb4.0.4使用tiup扩容TiKV 节点的更多相关文章

随机推荐

热门专题