Issue with monitoring_servers: Port 9090 conflict with systemd process 9090 during single server installation

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

Original topic: monitoring_servers 在单台服务器安装中出现9090端口与systemd 进程9090冲突问题

| username: bulibuqiyaoyao133

【TiDB Usage Environment】Production\Test Environment\POC
【TiDB Version】6.1.0
【Encountered Problem】The 9090 port of monitoring_servers conflicts with the systemd process 9090 during single server installation.
【Reproduction Path】Modified the monitoring_servers port in the yaml file and ran it, but could not run the port separately.
monitoring_servers:

  • host: 10.0.1.123

    ssh_port: 22

    port: 9090

    deploy_dir: “/mnt/data/tidb-deploy/prometheus-8249”

    data_dir: “/mnt/data/tidb-data/prometheus-8249”

    log_dir: “/mnt/data/tidb-deploy/prometheus-8249/log”

【Problem Phenomenon and Impact】
Cannot start the 9090 port after the conflict.

| username: bulibuqiyaoyao133 | Original post link

The image is not visible. Please provide the text you need translated.

| username: bulibuqiyaoyao133 | Original post link

The default value of tidb_dml_batch_size is 2000. If the batch size is too large, it may cause the transaction to be too large and affect performance. If the batch size is too small, it may cause too many transactions and affect performance. You can adjust this parameter according to your actual situation.

| username: TiDBer_wTKU9jv6 | Original post link

Modify the port ng_port in monitoring_servers.

| username: bulibuqiyaoyao133 | Original post link

Is it added like this in the yaml file?

monitoring_servers:
  port: ng_port 9190
| username: TiDBer_wTKU9jv6 | Original post link

The image is not visible. Please provide the text you need translated.

| username: bulibuqiyaoyao133 | Original post link

# Monitored variables are applied to all the machines.

monitored:
node_exporter_port: 9100
blackbox_exporter_port: 9115

server_configs:
tidb:
log.slow-threshold: 300
tikv:
readpool.storage.use-unified-pool: false
readpool.coprocessor.use-unified-pool: true
pd:
replication.enable-placement-rules: true
replication.location-labels: [“host”]
tiflash:
logger.level: “info”

pd_servers:

  • host: 10.0.1.123

tidb_servers:

  • host: 10.0.1.123

tikv_servers:

  • host: 10.0.1.123
    port: 20160
    status_port: 20180
    config:
    server.labels: { host: “logic-host-1” }

  • host: 10.0.1.123
    port: 20161
    status_port: 20181
    config:
    server.labels: { host: “logic-host-2” }

  • host: 10.0.1.123
    port: 20162
    status_port: 20182
    config:
    server.labels: { host: “logic-host-3” }

tiflash_servers:

  • host: 10.0.1.123

monitoring_servers:

  • host: 10.0.1.123
    port: 9190
    ng_port: 21183

grafana_servers:

  • host: 10.0.1.123
| username: bulibuqiyaoyao133 | Original post link

Hello, this is how I wrote it. Is it okay? Thanks.

| username: TiDBer_wTKU9jv6 | Original post link

Sure, go ahead and deploy it to give it a try.

| username: bulibuqiyaoyao133 | Original post link

Sorry, I can’t translate the content from the image. Please provide the text you need translated.

| username: bulibuqiyaoyao133 | Original post link

Thank you, it seems the problem is solved.

| username: bulibuqiyaoyao133 | Original post link

The image you provided cannot be translated directly as it is not text-based. Please provide the text content for translation.

| username: TiDBer_wTKU9jv6 | Original post link

:ok_hand::+1:

| username: system | Original post link

This topic was automatically closed 1 minute after the last reply. No new replies are allowed.