Configuration

GreptimeDB supports layered configuration with the following precedence order (where each item overrides the one below it):

  • Greptime command line options
  • Configuration file options
  • Environment variables
  • Default values

You only need to set up the configurations you require. GreptimeDB will assign default values for any settings not configured.

How to set up configurations

Greptime command line options

You can specify several configurations using command line arguments. For example, to start GreptimeDB in standalone mode with a configured HTTP address:

  1. greptime standalone start --http-addr 127.0.0.1:4000

For all the options supported by the Greptime command line, refer to the GreptimeDB Command Line Interface.

Configuration file options

You can specify configurations in a TOML file. For example, create a configuration file standalone.example.toml as shown below:

  1. [storage]
  2. type = "File"
  3. data_home = "/tmp/greptimedb/"

Then, specify the configuration file using the command line argument -c [file_path].

  1. greptime [standalone | frontend | datanode | metasrv] start -c config/standalone.example.toml

For example, to start in standalone mode:

  1. greptime standalone start -c standalone.example.toml

Example files

Below are example configuration files for each GreptimeDB component, including all available configurations. In actual scenarios, you only need to configure the required options and do not need to configure all options as in the sample file.

Environment variable

Every item in the configuration file can be mapped to environment variables. For example, to set the data_home configuration item for the datanode using an environment variable:

  1. # ...
  2. [storage]
  3. data_home = "/data/greptimedb"
  4. # ...

Use the following shell command to set the environment variable in the following format:

  1. export GREPTIMEDB_DATANODE__STORAGE__DATA_HOME=/data/greptimedb

Environment Variable Rules

  • Each environment variable should have the component prefix, for example:

    • GREPTIMEDB_FRONTEND
    • GREPTIMEDB_METASRV
    • GREPTIMEDB_DATANODE
    • GREPTIMEDB_STANDALONE
  • Use double underscore __ separators. For example, the data structure storage.data_home is transformed to STORAGE__DATA_HOME.

The environment variable also accepts lists that are separated by commas ,, for example:

  1. GREPTIMEDB_METASRV__META_CLIENT__METASRV_ADDRS=127.0.0.1:3001,127.0.0.1:3002,127.0.0.1:3003

Options

In this section, we will introduce some main configuration options. For all options, refer to the Configuration Reference on Github.

Protocol options

Protocol options are valid in frontend and standalone subcommands, specifying protocol server addresses and other protocol-related options.

Below is an example configuration with default values. You can change the values or disable certain protocols in your configuration file. For example, to disable OpenTSDB protocol support, set the enable parameter to false. Note that HTTP and gRPC protocols cannot be disabled for the database to function correctly.

  1. [http]
  2. addr = "127.0.0.1:4000"
  3. timeout = "30s"
  4. body_limit = "64MB"
  5. [grpc]
  6. addr = "127.0.0.1:4001"
  7. runtime_size = 8
  8. [mysql]
  9. enable = true
  10. addr = "127.0.0.1:4002"
  11. runtime_size = 2
  12. [mysql.tls]
  13. mode = "disable"
  14. cert_path = ""
  15. key_path = ""
  16. [postgres]
  17. enable = true
  18. addr = "127.0.0.1:4003"
  19. runtime_size = 2
  20. [postgres.tls]
  21. mode = "disable"
  22. cert_path = ""
  23. key_path = ""
  24. [opentsdb]
  25. enable = true
  26. [influxdb]
  27. enable = true
  28. [prom_store]
  29. enable = true
  30. with_metric_engine = true

The following table describes the options in detail:

OptionKeyTypeDescription
httpHTTP server options
addrStringServer address, “127.0.0.1:4000” by default
timeoutStringHTTP request timeout, “30s” by default
body_limitStringHTTP max body size, “64MB” by default
is_strict_modeBooleanWhether to enable the strict verification mode of the protocol, which will slightly affect performance. False by default.
grpcgRPC server options
addrStringServer address, “127.0.0.1:4001” by default
runtime_sizeIntegerThe number of server worker threads, 8 by default
mysqlMySQL server options
enableBooleanWhether to enable MySQL protocol, true by default
addrStringServer address, “127.0.0.1:4002” by default
runtime_sizeIntegerThe number of server worker threads, 2 by default
influxdbInfluxDB Protocol options
enableBooleanWhether to enable InfluxDB protocol in HTTP API, true by default
opentsdbOpenTSDB Protocol options
enableBooleanWhether to enable OpenTSDB protocol in HTTP API, true by default
prom_storePrometheus remote storage options
enableBooleanWhether to enable Prometheus Remote Write and read in HTTP API, true by default
with_metric_engineBooleanWhether to use the metric engine on Prometheus Remote Write, true by default
postgresPostgresSQL server options
enableBooleanWhether to enable PostgresSQL protocol, true by default
addrStringServer address, “127.0.0.1:4003” by default
runtime_sizeIntegerThe number of server worker threads, 2 by default

Storage options

The storage options are valid in datanode and standalone mode, which specify the database data directory and other storage-related options.

GreptimeDB supports storing data in local file system, AWS S3 and compatible services (including MinIO, digitalocean space, Tencent Cloud Object Storage(COS), Baidu Object Storage(BOS) and so on), Azure Blob Storage and Aliyun OSS.

OptionKeyTypeDescription
storageStorage options
typeStringStorage type, supports “File”, “S3” and “Oss” etc.
FileLocal file storage options, valid when type=”File”
data_homeStringDatabase storage root directory, “/tmp/greptimedb” by default
S3AWS S3 storage options, valid when type=”S3”
bucketStringThe S3 bucket name
rootStringThe root path in S3 bucket
endpointStringThe API endpoint of S3
regionStringThe S3 region
access_key_idStringThe S3 access key id
secret_access_keyStringThe S3 secret access key
OssAliyun OSS storage options, valid when type=”Oss”
bucketStringThe OSS bucket name
rootStringThe root path in OSS bucket
endpointStringThe API endpoint of OSS
access_key_idStringThe OSS access key id
secret_access_keyStringThe OSS secret access key
AzblobAzure Blob Storage options, valid when type=”Azblob”
containerStringThe container name
rootStringThe root path in container
endpointStringThe API endpoint of Azure Blob Storage
account_nameStringThe account name of Azure Blob Storage
account_keyStringThe access key
sas_tokenStringThe shared access signature
GscGoogle Cloud Storage options, valid when type=”Gsc”
rootStringThe root path in Gsc bucket
bucketStringThe Gsc bucket name
scopeStringThe Gsc service scope
credential_pathStringThe Gsc credentials path
endpointStringThe API endpoint of Gsc

A file storage sample configuration:

  1. [storage]
  2. type = "File"
  3. data_home = "/tmp/greptimedb/"

A S3 storage sample configuration:

  1. [storage]
  2. type = "S3"
  3. bucket = "test_greptimedb"
  4. root = "/greptimedb"
  5. access_key_id = "<access key id>"
  6. secret_access_key = "<secret access key>"

Storage engine provider

[[storage.providers]] setups the table storage engine providers. Based on these providers, you can create a table with a specified storage, see create table:

  1. # Allows using multiple storages
  2. [[storage.providers]]
  3. type = "S3"
  4. bucket = "test_greptimedb"
  5. root = "/greptimedb"
  6. access_key_id = "<access key id>"
  7. secret_access_key = "<secret access key>"
  8. [[storage.providers]]
  9. type = "Gcs"
  10. bucket = "test_greptimedb"
  11. root = "/greptimedb"
  12. credential_path = "<gcs credential path>"

All configured providers can be used as the storage option when creating tables.

Object storage cache

When using S3, OSS or Azure Blob Storage, it’s better to enable object storage caching for speedup data querying:

  1. [storage]
  2. type = "S3"
  3. bucket = "test_greptimedb"
  4. root = "/greptimedb"
  5. access_key_id = "<access key id>"
  6. secret_access_key = "<secret access key>"
  7. ## Enable object storage caching
  8. cache_path = "/var/data/s3_local_cache"
  9. cache_capacity = "256MiB"

The cache_path is the local file directory that keeps cache files, and the cache_capacity is the maximum total file size in the cache directory.

WAL options

The [wal] section in datanode or standalone config file configures the options of Write-Ahead-Log:

Local WAL

  1. [wal]
  2. provider = "raft_engine"
  3. file_size = "256MB"
  4. purge_threshold = "4GB"
  5. purge_interval = "10m"
  6. read_batch_size = 128
  7. sync_write = false
  • dir: is the directory where to write logs. When using File storage, it’s {data_home}/wal by default. It must be configured explicitly when using other storage types such as S3 etc.
  • file_size: the maximum size of the WAL log file, default is 256MB.
  • purge_threshold and purge_interval: control the purging of wal files, default is 4GB.
  • sync_write: whether to call fsync when writing every log.

Remote WAL

  1. [wal]
  2. provider = "kafka"
  3. broker_endpoints = ["127.0.0.1:9092"]
  4. max_batch_bytes = "1MB"
  5. consumer_wait_timeout = "100ms"
  6. backoff_init = "500ms"
  7. backoff_max = "10s"
  8. backoff_base = 2
  9. backoff_deadline = "5mins"
  • broker_endpoints: The Kafka broker endpoints.
  • max_batch_bytes: The max size of a single producer batch.
  • consumer_wait_timeout: The consumer wait timeout.
  • backoff_init: The initial backoff delay.
  • backoff_max: The maximum backoff delay.
  • backoff_base: The exponential backoff rate.
  • backoff_deadline: The deadline of retries.
Remote WAL Authentication (Optional)
  1. [wal.sasl]
  2. type = "SCRAM-SHA-512"
  3. username = "user"
  4. password = "secret"

The SASL configuration for Kafka client, available SASL mechanisms: PLAIN, SCRAM-SHA-256, SCRAM-SHA-512.

Remote WAL TLS (Optional)
  1. [wal.tls]
  2. server_ca_cert_path = "/path/to/server_cert"
  3. client_cert_path = "/path/to/client_cert"
  4. client_key_path = "/path/to/key"

The TLS configuration for Kafka client, support modes: TLS (using system ca certs), TLS (with specified ca certs), mTLS.

Examples:

TLS (using system ca certs)

  1. [wal.tls]

TLS (with specified ca cert)

  1. [wal.tls]
  2. server_ca_cert_path = "/path/to/server_cert"

mTLS

  1. [wal.tls]
  2. server_ca_cert_path = "/path/to/server_cert"
  3. client_cert_path = "/path/to/client_cert"
  4. client_key_path = "/path/to/key"

Logging options

frontend, metasrv, datanode and standalone can all configure log and tracing related parameters in the [logging] section:

  1. [logging]
  2. dir = "/tmp/greptimedb/logs"
  3. level = "info"
  4. enable_otlp_tracing = false
  5. otlp_endpoint = "localhost:4317"
  6. append_stdout = true
  7. [logging.tracing_sample_ratio]
  8. default_ratio = 1.0
  • dir: log output directory.
  • level: output log level, available log level are info, debug, error, warn, the default level is info.
  • enable_otlp_tracing: whether to turn on tracing, not turned on by default.
  • otlp_endpoint: Export the target endpoint of tracing using gRPC-based OTLP protocol, the default value is localhost:4317.
  • append_stdout: Whether to append logs to stdout. Defaults to true.
  • tracing_sample_ratio: This field can configure the sampling rate of tracing. How to use tracing_sample_ratio, please refer to How to configure tracing sampling rate.

How to use distributed tracing, please reference Tracing

Region engine options

The parameters corresponding to different storage engines can be configured for datanode and standalone in the [region_engine] section. Currently, only options for mito region engine is available.

Frequently used options:

  1. [[region_engine]]
  2. [region_engine.mito]
  3. num_workers = 8
  4. manifest_checkpoint_distance = 10
  5. max_background_jobs = 4
  6. auto_flush_interval = "1h"
  7. global_write_buffer_size = "1GB"
  8. global_write_buffer_reject_size = "2GB"
  9. sst_meta_cache_size = "128MB"
  10. vector_cache_size = "512MB"
  11. page_cache_size = "512MB"
  12. sst_write_buffer_size = "8MB"
  13. scan_parallelism = 0
  14. [region_engine.mito.inverted_index]
  15. create_on_flush = "auto"
  16. create_on_compaction = "auto"
  17. apply_on_query = "auto"
  18. mem_threshold_on_create = "64M"
  19. intermediate_path = ""
  20. [region_engine.mito.memtable]
  21. type = "time_series"

The mito engine provides an experimental memtable which optimizes for write performance and memory efficiency under large amounts of time-series. Its read performance might not as fast as the default time_series memtable.

  1. [region_engine.mito.memtable]
  2. type = "partition_tree"
  3. index_max_keys_per_shard = 8192
  4. data_freeze_threshold = 32768
  5. fork_dictionary_bytes = "1GiB"

Available options:

KeyTypeDefaultDescriptions
num_workersInteger8Number of region workers.
manifest_checkpoint_distanceInteger10Number of meta action updated to trigger a new checkpoint for the manifest.
max_background_jobsInteger4Max number of running background jobs
auto_flush_intervalString1hInterval to auto flush a region if it has not flushed yet.
global_write_buffer_sizeString1GBGlobal write buffer size for all regions. If not set, it’s default to 1/8 of OS memory with a max limitation of 1GB.
global_write_buffer_reject_sizeString2GBGlobal write buffer size threshold to reject write requests. If not set, it’s default to 2 times of global_write_buffer_size
sst_meta_cache_sizeString128MBCache size for SST metadata. Setting it to 0 to disable the cache.
If not set, it’s default to 1/32 of OS memory with a max limitation of 128MB.
vector_cache_sizeString512MBCache size for vectors and arrow arrays. Setting it to 0 to disable the cache.
If not set, it’s default to 1/16 of OS memory with a max limitation of 512MB.
page_cache_sizeString512MBCache size for pages of SST row groups. Setting it to 0 to disable the cache.
If not set, it’s default to 1/8 of OS memory.
selector_result_cache_sizeString512MBCache size for time series selector (e.g. last_value()). Setting it to 0 to disable the cache.
If not set, it’s default to 1/8 of OS memory.
sst_write_buffer_sizeString8MBBuffer size for SST writing.
scan_parallelismInteger0Parallelism to scan a region (default: 1/4 of cpu cores).
- 0: using the default value (1/4 of cpu cores).
- 1: scan in current thread.
- n: scan in parallelism n.
inverted_indexThe options for inverted index in Mito engine.
inverted_index.create_on_flushStringautoWhether to create the index on flush.
- auto: automatically
- disable: never
inverted_index.create_on_compactionStringautoWhether to create the index on compaction.
- auto: automatically
- disable: never
inverted_index.apply_on_queryStringautoWhether to apply the index on query
- auto: automatically
- disable: never
inverted_index.mem_threshold_on_createString64MMemory threshold for performing an external sort during index creation.
Setting to empty will disable external sorting, forcing all sorting operations to happen in memory.
inverted_index.intermediate_pathString“”File system path to store intermediate files for external sorting (default {data_home}/index_intermediate).
memtable.typeStringtime_seriesMemtable type.
- time_series: time-series memtable
- partition_tree: partition tree memtable (experimental)
memtable.index_max_keys_per_shardInteger8192The max number of keys in one shard.
Only available for partition_tree memtable.
memtable.data_freeze_thresholdInteger32768The max rows of data inside the actively writing buffer in one shard.
Only available for partition_tree memtable.
memtable.fork_dictionary_bytesString1GiBMax dictionary bytes.
Only available for partition_tree memtable.

Specify meta client

The meta_client options are valid in datanode and frontend mode, which specify the Metasrv client information.

  1. metasrv_addrs = ["127.0.0.1:3002"]
  2. timeout = "3s"
  3. connect_timeout = "1s"
  4. ddl_timeout = "10s"
  5. tcp_nodelay = true

The meta_client configures the Metasrv client, including:

  • metasrv_addrs: The Metasrv address list.
  • timeout: operation timeout, 3s by default.
  • connect_timeout, connect server timeout, 1s by default.
  • ddl_timeout, DDL execution timeout, 10s by default.
  • tcp_nodelay, TCP_NODELAY option for accepted connections, true by default.

Monitor metrics options

These options are used to save system metrics to GreptimeDB itself. For instructions on how to use this feature, please refer to the Monitoring guide.

  1. [export_metrics]
  2. # Whether to enable export_metrics
  3. enable=true
  4. # Export time interval
  5. write_interval = "30s"
  • enable: Whether to enable export_metrics, false by default.
  • write_interval: Export time interval.

self_import method

Only frontend and standalone support exporting metrics using self_import method.

  1. [export_metrics]
  2. # Whether to enable export_metrics
  3. enable=true
  4. # Export time interval
  5. write_interval = "30s"
  6. [export_metrics.self_import]
  7. db = "information_schema"
  • db: The default database used by self_import is information_schema. You can also create another database for saving system metrics.

remote_write method

The remote_write method is supported by datanode, frontend, metasrv, and standalone. It sends metrics to a receiver compatible with the Prometheus Remote-Write protocol.

  1. [export_metrics]
  2. # Whether to enable export_metrics
  3. enable=true
  4. # Export time interval
  5. write_interval = "30s"
  6. [export_metrics.remote_write]
  7. # URL specified by Prometheus Remote-Write protocol
  8. url = "http://127.0.0.1:4000/v1/prometheus/write?db=information_schema"
  9. # Some optional HTTP parameters, such as authentication information
  10. headers = { Authorization = "Basic Z3JlcHRpbWVfdXNlcjpncmVwdGltZV9wd2Q=" }
  • url: URL specified by Prometheus Remote-Write protocol.
  • headers: Some optional HTTP parameters, such as authentication information.

Mode option

The mode option is valid in datanode, frontend and standalone, which specify the running mode of the component.

In the configuration files of datanode and frontend of distributed GreptimeDB, the value needs to be set as distributed:

  1. mode = "distributed"

In the configuration files of standalone GreptimeDB, the value needs to be set as standalone:

  1. mode = "standalone"

Metasrv-only configuration

  1. # The working home directory.
  2. data_home = "/tmp/metasrv/"
  3. # The bind address of metasrv, "127.0.0.1:3002" by default.
  4. bind_addr = "127.0.0.1:3002"
  5. # The communication server address for frontend and datanode to connect to metasrv, "127.0.0.1:3002" by default for localhost.
  6. server_addr = "127.0.0.1:3002"
  7. # Store server address, "127.0.0.1:2379" by default with etcd store.
  8. store_addr = "127.0.0.1:2379"
  9. # Datanode selector type.
  10. # - "lease_based" (default value).
  11. # - "load_based"
  12. # For details, please see "https://docs.greptime.com/contributor-guide/meta/selector".
  13. selector = "LeaseBased"
  14. # Store data in memory, false by default.
  15. use_memory_store = false
  16. ## Whether to enable region failover.
  17. ## This feature is only available on GreptimeDB running on cluster mode and
  18. ## - Using Remote WAL
  19. ## - Using shared storage (e.g., s3).
  20. enable_region_failover = false
  21. # The datastore for meta server.
  22. backend = "EtcdStore"
  23. ## Procedure storage options.
  24. [procedure]
  25. ## Procedure max retry time.
  26. max_retry_times = 12
  27. ## Initial retry delay of procedures, increases exponentially
  28. retry_delay = "500ms"
  29. # Failure detectors options.
  30. [failure_detector]
  31. ## The threshold value used by the failure detector to determine failure conditions.
  32. threshold = 8.0
  33. ## The minimum standard deviation of the heartbeat intervals, used to calculate acceptable variations.
  34. min_std_deviation = "100ms"
  35. ## The acceptable pause duration between heartbeats, used to determine if a heartbeat interval is acceptable.
  36. acceptable_heartbeat_pause = "10000ms"
  37. ## The initial estimate of the heartbeat interval used by the failure detector.
  38. first_heartbeat_estimate = "1000ms"
  39. ## Datanode options.
  40. [datanode]
  41. ## Datanode client options.
  42. [datanode.client]
  43. ## Operation timeout.
  44. timeout = "10s"
  45. ## Connect server timeout.
  46. connect_timeout = "10s"
  47. ## `TCP_NODELAY` option for accepted connections.
  48. tcp_nodelay = true
  49. [wal]
  50. # Available wal providers:
  51. # - `raft_engine` (default): there're none raft-engine wal config since metasrv only involves in remote wal currently.
  52. # - `kafka`: metasrv **have to be** configured with kafka wal config when using kafka wal provider in datanode.
  53. provider = "raft_engine"
  54. # Kafka wal config.
  55. ## The broker endpoints of the Kafka cluster.
  56. broker_endpoints = ["127.0.0.1:9092"]
  57. ## Automatically create topics for WAL.
  58. ## Set to `true` to automatically create topics for WAL.
  59. ## Otherwise, use topics named `topic_name_prefix_[0..num_topics)`
  60. auto_create_topics = true
  61. ## Number of topics.
  62. num_topics = 64
  63. ## Topic selector type.
  64. ## Available selector types:
  65. ## - `round_robin` (default)
  66. selector_type = "round_robin"
  67. ## A Kafka topic is constructed by concatenating `topic_name_prefix` and `topic_id`.
  68. topic_name_prefix = "greptimedb_wal_topic"
  69. ## Expected number of replicas of each partition.
  70. replication_factor = 1
  71. ## Above which a topic creation operation will be cancelled.
  72. create_topic_timeout = "30s"
  73. ## The initial backoff for kafka clients.
  74. backoff_init = "500ms"
  75. ## The maximum backoff for kafka clients.
  76. backoff_max = "10s"
  77. ## Exponential backoff rate, i.e. next backoff = base * current backoff.
  78. backoff_base = 2
  79. ## Stop reconnecting if the total wait time reaches the deadline. If this config is missing, the reconnecting won't terminate.
  80. backoff_deadline = "5mins"
  81. # The Kafka SASL configuration.
  82. # **It's only used when the provider is `kafka`**.
  83. # Available SASL mechanisms:
  84. # - `PLAIN`
  85. # - `SCRAM-SHA-256`
  86. # - `SCRAM-SHA-512`
  87. # [wal.sasl]
  88. # type = "SCRAM-SHA-512"
  89. # username = "user_kafka"
  90. # password = "secret"
  91. # The Kafka TLS configuration.
  92. # **It's only used when the provider is `kafka`**.
  93. # [wal.tls]
  94. # server_ca_cert_path = "/path/to/server_cert"
  95. # client_cert_path = "/path/to/client_cert"
  96. # client_key_path = "/path/to/key"
KeyTypeDefaultDescriptions
datahomeString/tmp/metasrv/The working home directory.
bind_addrString127.0.0.1:3002The bind address of metasrv.
server_addrString127.0.0.1:3002The communication server address for frontend and datanode to connect to metasrv, “127.0.0.1:3002” by default for localhost.
store_addrString127.0.0.1:2379Etcd server address.
selectorStringlease_basedDatanode selector type.
- lease_based (default value).
- load_based
For details, see Selector
use_memory_storeBoolfalseStore data in memory.
enable_region_failoverBoolfalseWhether to enable region failover.
This feature is only available on GreptimeDB running on cluster mode and
- Using Remote WAL
- Using shared storage (e.g., s3).
procedureProcedure storage options.
procedure.max_retry_timesInteger12Procedure max retry time.
procedure.retry_delayString500msInitial retry delay of procedures, increases exponentially
failure_detector
failure_detector.thresholdFloat8.0The threshold value used by the failure detector to determine failure conditions.
failure_detector.min_std_deviationString100msThe minimum standard deviation of the heartbeat intervals, used to calculate acceptable variations.
failure_detector.acceptable_heartbeat_pauseString10000msThe acceptable pause duration between heartbeats, used to determine if a heartbeat interval is acceptable.
failure_detector.first_heartbeat_estimateString1000msThe initial estimate of the heartbeat interval used by the failure detector.
datanodeDatanode options.
datanode.clientDatanode client options.
datanode.client.timeoutString10sOperation timeout.
datanode.client.connect_timeoutString10sConnect server timeout.
datanode.client.tcp_nodelayBooltrueTCP_NODELAY option for accepted connections.
wal
wal.providerStringraft_engine
wal.broker_endpointsArrayThe broker endpoints of the Kafka cluster.
wal.auto_create_topicsBooltrueAutomatically create topics for WAL.
Set to true to automatically create topics for WAL.
Otherwise, use topics named topic_name_prefix[0..num_topics)
wal.num_topicsInteger64Number of topics.
wal.selector_typeStringround_robinTopic selector type.
Available selector types:
- round_robin (default)
wal.topic_name_prefixStringgreptimedb_wal_topicA Kafka topic is constructed by concatenating topic_name_prefix and topic_id.
wal.replication_factorInteger1Expected number of replicas of each partition.
wal.create_topic_timeoutString30sAbove which a topic creation operation will be cancelled.
wal.backoff_initString500msThe initial backoff for kafka clients.
wal.backoff_maxString10sThe maximum backoff for kafka clients.
wal.backoff_baseInteger2Exponential backoff rate, i.e. next backoff = base * current backoff.
wal.backoff_deadlineString5minsStop reconnecting if the total wait time reaches the deadline. If this config is missing, the reconnecting won’t terminate.
wal.saslStringThe Kafka SASL configuration.
wal.sasl.typeStringThe SASL mechanisms, available values: PLAIN, SCRAM-SHA-256, SCRAM-SHA-512.
wal.sasl.usernameStringThe SASL username.
wal.sasl.passwordStringThe SASL password.
wal.tlsStringThe Kafka TLS configuration.
wal.tls.server_ca_cert_pathStringThe path of trusted server ca certs.
wal.tls.client_cert_pathStringThe path of client cert (Used for enable mTLS).
wal.tls.client_key_pathStringThe path of client key (Used for enable mTLS).

Datanode-only configuration

  1. node_id = 42
  2. rpc_hostname = "127.0.0.1"
  3. rpc_addr = "127.0.0.1:3001"
  4. rpc_runtime_size = 8
KeyTypeDescription
node_idIntegerThe datanode identifier, should be unique.
rpc_hostnameStringHostname of this node.
rpc_addrStringgRPC server address, “127.0.0.1:3001” by default.
rpc_runtime_sizeIntegerThe number of gRPC server worker threads, 8 by default.