TiProxy Configuration File

This document introduces the configuration parameters related to the deployment and use of TiProxy. The following is an example configuration:

[proxy]
addr = "0.0.0.0:6000"
max-connections = 100

[api]
addr = "0.0.0.0:3080"

[log]
level = "info"

[security]
[security.cluster-tls]
skip-ca = true

[security.sql-tls]
skip-ca = true

Configure the tiproxy.toml file

This section introduces the configuration parameters of TiProxy.

proxy

Configuration for SQL port.

addr

• Default value: 0.0.0.0:6000
• Support hot-reload: no
• SQL gateway address. The format is <ip>:<port>.

graceful-wait-before-shutdown

• Default value: 0
• Support hot-reload: yes
• Unit: second
• When TiProxy shuts down, the HTTP status returns unhealthy but the SQL port still accepts new connections for graceful-wait-before-shutdown seconds. After that, it rejects new connections and drains clients. It is recommended to set it to 0 when there are no other proxies (e.g. NLB) between the client and TiProxy.

graceful-close-conn-timeout

• Default value: 15
• Support hot-reload: yes
• Unit: second
• When TiProxy shuts down, it closes connections when they have completed their current transactions (also known as draining clients) within graceful-close-conn-timeout seconds. After that, all the connections are closed at once. graceful-close-conn-timeout happens after graceful-wait-before-shutdown. It is recommended to set this timeout longer than the lifecycle of a transaction.

max-connections

• Default value: 0
• Support hot-reload: yes
• Each TiProxy instance can accept max-connections connections at most. 0 means no limitation.

conn-buffer-size

• Default value: 32768
• Support hot-reload: yes, but only for new connections
• Range: [1024, 16777216]
• This configuration item lets you decide the connection buffer size. Each connection uses one read buffer and one write buffer. It is a tradeoff between memory and performance. A larger buffer might yield better performance results but consume more memory. When it is 0, TiProxy uses the default buffer size.

pd-addrs

• Default value: 127.0.0.1:2379
• Support hot-reload: no
• The PD addresses TiProxy connects to. TiProxy discovers TiDB instances by fetching the TiDB list from the PD. It is set automatically when TiProxy is deployed by TiUP or TiDB Operator.

proxy-protocol

• Default value: ""
• Support hot-reload: yes, but only for new connections
• Possible values: "", "v2"
• Enable the PROXY protocol on the port. By enabling the PROXY protocol, TiProxy can pass the real client IP address to TiDB. "v2" indicates using the PROXY protocol version 2, and "" indicates disabling the PROXY protocol. If the PROXY protocol is enabled on TiProxy, you need to also enable the PROXY protocol on the TiDB server.

api

Configurations for HTTP gateway.

addr

• Default value: 0.0.0.0:3080
• Support hot-reload: no
• API gateway address. You can specify ip:port.

proxy-protocol

• Default value: ""
• Support hot-reload: no
• Possible values: "", "v2"
• Enable the PROXY protocol on the port. "v2" indicates using the PROXY protocol version 2, and "" indicates disabling the PROXY protocol.

log

level

• Default value: info
• Support hot-reload: yes
• Possible values: debug, info, warn, error, panic
• Specify the log level. With the panic level, TiProxy will panic on errors.

encoder

• Default value: tidb

• You can specify:

  • tidb: format used by TiDB. For details, refer to Unified Log Format.
  • json: structured JSON format.
  • console: human-readable log format.

log.log-file

filename

• Default value: ""
• Support hot-reload: yes
• Log file path. Non empty value will enable logging to file. When TiProxy is deployed with TiUP, the filename is set automatically.

max-size

• Default value: 300
• Support hot-reload: yes
• Unit: MB
• Specifies the maximum size for log files. A log file will be rotated if its size exceeds this limit.

max-days

• Default value: 3
• Support hot-reload: yes
• Specifies the maximum number of days to keep old log files. Outdated log files are deleted after surpassing this period.

max-backups

• Default value: 3
• Support hot-reload: yes
• Specifies the maximum number of log files to be retained. Surplus log files will be automatically deleted when an excessive number is reached.

security

There are four TLS objects in the [security] section with different names. They share the same configuration format and fields, but they are interpreted differently depending on their names.

[security]
    [sql-tls]
    skip-ca = true
    [server-tls]
    auto-certs = true

All TLS options are hot-reloaded.

TLS object fields:

• ca: specifies the CA
• cert: specifies the certificate
• key: specifies the private key
• auto-certs: mostly used for tests. It generates certificates if no certificate or key is specified.
• skip-ca: skips verifying certificates using CA on client object or skips server-side verification on server object.
• min-tls-version: sets the minimum TLS version. Possible values are 1.0、1.1、1.2, and 1.3. The default value is 1.2, which allows v1.2 or higher TLS versions.
• rsa-key-size: sets the RSA key size when auto-certs is enabled.
• autocert-expire-duration: sets the default expiration duration for auto-generated certificates.

Objects are classified into client or server objects by their names.

For client TLS object:

• You must set either ca or skip-ca to skip verifying server certificates.
• Optionally, you can set cert or key to pass server-side client verification.
• Useless fields: auto-certs.

For server TLS object:

• You can set either cert or key or auto-certs to support TLS connections. Otherwise, TiProxy doesn't support TLS connections.
• Optionally, if ca is not empty, it enables server-side client verification. The client must provide their certificates. Alternatively, if both skip-ca is true and ca is not empty, the server will only verify client certificates if they provide one.

cluster-tls

A client TLS object. It is used to access TiDB or PD.

require-backend-tls

• Default value: false
• Support hot-reload: yes, but only for new connections
• Require TLS between TiProxy and TiDB servers. If the TiDB server does not support TLS, clients will report an error when connecting to TiProxy.

sql-tls

A client TLS object. It is used to access TiDB SQL port (4000).

server-tls

A server TLS object. It is used to provide TLS on SQL port (6000).

server-http-tls

A server TLS object. It is used to provide TLS on HTTP status port (3080).