From 8e10d31e69caba6d378f35339a510bf657de6903 Mon Sep 17 00:00:00 2001 From: lilin90 Date: Mon, 16 Dec 2024 17:26:29 +0800 Subject: [PATCH] Update production-deployment-using-tiup.md --- production-deployment-using-tiup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/production-deployment-using-tiup.md b/production-deployment-using-tiup.md index d2846e93941ed..83e8d7d562cd1 100644 --- a/production-deployment-using-tiup.md +++ b/production-deployment-using-tiup.md @@ -10,7 +10,7 @@ This guide describes how to deploy a TiDB Self-Managed cluster using [TiUP](http TiUP is a cluster operation and maintenance tool introduced in TiDB 4.0. It provides [TiUP cluster](https://github.com/pingcap/tiup/tree/master/components/cluster), a Golang-based component for managing TiDB clusters. By using the TiUP cluster, you can easily perform routine database operations, such as deploying, starting, stopping, destroying, scaling, upgrading TiDB clusters, and managing TiDB cluster parameters. -TiUP also supports deploying TiDB, TiFlash, TiCDC, and the monitoring system. This document introduces how to deploy TiDB clusters with different topologies. +TiUP also supports deploying TiDB, TiFlash, TiCDC, and the monitoring system. This guide introduces how to deploy TiDB clusters with different topologies. ## Step 1. Prerequisites and precheck