Deployments & Administration

This section covers running GreptimeDB on your own infrastructure. Start with Architecture to see which components you will deploy and operate. GreptimeCloud runs the same engine as a managed service, with deployment and maintenance handled for you.

Deploy

• Configuration — protocol, storage, and runtime settings to review before the first deployment.
• Deploy on Kubernetes — deployment through the GreptimeDB Operator.
• Capacity Planning — sizing compute, memory, and local cache for the expected ingestion rate and query mix.
• Authentication — not enabled by default.
• Run on Android — for edge deployments on Android devices.

Operate

• Monitoring — cluster health and performance through metrics, tracing, and runtime information.
• Table and Region Operations — table operations, sharding, Region migration and failover, repartition, compaction, and garbage collection.
• Metadata Storage — the metadata backend the cluster depends on.
• Maintenance — maintenance mode, recovery mode, table reconciliation, and sequence management.
• Upgrade — moving a deployment to a newer version.
• Troubleshooting — collecting the information needed to diagnose a problem.

Durability and recovery

• Write-Ahead Logging (WAL) — local and Remote WAL, including the Remote WAL setup that cluster failover depends on.
• Disaster Recovery — backup, restore, and cross-region options.

Performance

• Performance Tuning — cache, query, and ingestion settings to adjust from runtime evidence.
• Design Table Schema — primary keys, indexes, append-only mode, and partitioning.