# Deploying a New `TiDB` Cluster that Includes `TiCDC`

+ Configure item **`cdc_servers`** in the `TiDB` cluster topology file, for example: **`topology.yaml`** 

```
~!@// File topology.yaml@!~
...
~!@cdc_servers:@!~
  - host: 10.0.0.150
    port: 8300
    deploy_dir: "/tidb-deploy/cdc-8300"
    data_dir: "/tidb-data/cdc-8300"
    log_dir: "/tidb-deploy/cdc-8300/log"
    gc-ttl: 86400 
 ...
```
```
$ tiup cluster ~!@deploy@!~ {cluster_name} v6.5.0 ./topology.yaml

```
```
```
-------------------------------------------------------------
When you deploy a new `TiDB` cluster using `TiUP`, you can also deploy `TiCDC` at the same time. You only need to add the `cdc_servers` section in the initialization configuration file that `TiUP` uses to start the `TiDB` cluster. 


`gc-ttl:` The `TTL (Time To Live)` of the service level `GC` safepoint in `PD` set by `TiCDC`, and the duration that the replication task can suspend, in seconds. The default value is 86400, which means 24 hours. Note: Suspending of the `TiCDC` replication task affects the progress of `TiCDC GC safepoint`, which means that it affects the progress of upstream `TiDB GC`