TiKV Scaling

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tikv扩容

| username: 等一分钟

When expanding TiKV nodes, the ssh_port parameter does not work and it keeps connecting to port 22.

2
| username: 等一分钟 | Original post link

The default value of tidb_dml_batch_size is 2000. You can adjust it according to your needs.

3
| username: 我是咖啡哥 | Original post link

Run tiup cluster show-config xx to check your current configuration.
Also, what command did you execute?

4
| username: 等一分钟 | Original post link

tiup cluster scale-out huawei_pt 1.yaml --user tidb -p

5
| username: 等一分钟 | Original post link

I need to add a new TiKV node.

6
| username: 我是咖啡哥 | Original post link

There doesn’t seem to be any issue with the configuration file for scaling.
So I want to take a look at your current global configuration.

7
| username: 等一分钟 | Original post link

global:
user: tidb
ssh_port: 10086
ssh_type: builtin
deploy_dir: /data/tidb-deploy
data_dir: /data/tidb-data
os: linux
arch: amd64
monitored:
node_exporter_port: 9100
blackbox_exporter_port: 9115
deploy_dir: /data/tidb-deploy/monitor-9100
data_dir: /data/tidb-data/monitor-9100
log_dir: /data/tidb-deploy/monitor-9100/log
server_configs:
tidb: {}
tikv: {}
pd: {}
tidb_dashboard: {}
tiflash: {}
tiflash-learner: {}
pump: {}
drainer: {}
cdc: {}
kvcdc: {}
grafana: {}
tidb_servers:

  • host: 172.26.200.169
    ssh_port: 10086
    port: 4000
    status_port: 10080
    deploy_dir: /data/tidb-deploy/tidb-4000
    log_dir: /data/tidb-deploy/tidb-4000/log
    arch: amd64
    os: linux
  • host: 172.26.200.202
    ssh_port: 10086
    port: 4000
    status_port: 10080
    deploy_dir: /data/tidb-deploy/tidb-4000
    log_dir: /data/tidb-deploy/tidb-4000/log
    arch: amd64
    os: linux
    tikv_servers:
  • host: 172.26.200.185
    ssh_port: 10086
    port: 20160
    status_port: 20180
    deploy_dir: /data/tidb-deploy/tikv-20160
    data_dir: /data/tidb-data/tikv-20160
    log_dir: /data/tidb-deploy/tikv-20160/log
    arch: amd64
    os: linux
  • host: 172.26.200.135
    ssh_port: 10086
    port: 20160
    status_port: 20180
    deploy_dir: /data/tidb-deploy/tikv-20160
    data_dir: /data/tidb-data/tikv-20160
    log_dir: /data/tidb-deploy/tikv-20160/log
    arch: amd64
    os: linux
    tiflash_servers:
    pd_servers:
  • host: 172.26.200.169
    ssh_port: 10086
    name: pd-172.26.200.169-2379
    client_port: 2379
    peer_port: 2380
    deploy_dir: /data/tidb-deploy/pd-2379
    data_dir: /data/tidb-data/pd-2379
    log_dir: /data/tidb-deploy/pd-2379/log
    arch: amd64
    os: linux
  • host: 172.26.200.202
    ssh_port: 10086
    name: pd-172.26.200.202-2379
    client_port: 2379
    peer_port: 2380
    deploy_dir: /data/tidb-deploy/pd-2379
    data_dir: /data/tidb-data/pd-2379
    log_dir: /data/tidb-deploy/pd-2379/log
    arch: amd64
    os: linux
    monitoring_servers:
  • host: 172.26.200.169
    ssh_port: 10086
    port: 9090
    ng_port: 12020
    deploy_dir: /data/tidb-deploy/prometheus-9090
    data_dir: /data/tidb-data/prometheus-9090
    log_dir: /data/tidb-deploy/prometheus-9090/log
    external_alertmanagers:
    arch: amd64
    os: linux
    grafana_servers:
  • host: 172.26.200.169
    ssh_port: 10086
    port: 3000
    deploy_dir: /data/tidb-deploy/grafana-3000
    arch: amd64
    os: linux
    username: admin
    password: admin
    anonymous_enable: false
    root_url: “”
    domain: “”
    alertmanager_servers:
  • host: 172.26.200.169
    ssh_port: 10086
    web_port: 9093
    cluster_port: 9094
    deploy_dir: /data/tidb-deploy/alertmanager-9093
    data_dir: /data/tidb-data/alertmanager-9093
    log_dir: /data/tidb-deploy/alertmanager-9093/log
    arch: amd64
    os: linux
8
| username: 等一分钟 | Original post link

This cluster is newly created. The machine that was supposed to be scaled out was originally deployed together, but it has been using port 22 all along. So I tried scaling out separately, but it still doesn’t seem to work.

9
| username: 等一分钟 | Original post link

Okay, it’s an issue with the directory permissions on that machine.

10
| username: 我是咖啡哥 | Original post link

I see. The prompt message didn’t include the port, which was misleading.

11
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.