Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
* updated doc
  • Loading branch information
Maksim Davydov committed Dec 20, 2024
1 parent 301230e commit 84a6d2e
Showing 1 changed file with 14 additions and 14 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -563,7 +563,7 @@ Basically, you can combine them any way you want to meet your project goals.

=== CDC example manager

`ignite-cdc-ext` ships with CDC example manager `cdc-start-up.sh` alongside `kafka-to-ignite.sh`
`ignite-cdc-ext` ships with CDC example manager `cdc-start-up.sh` alongside `kafka-to-ignite.sh`. You can find it under '../examples/config/cdc-start-up/' directory.

You can use this script to start all kinds of replication strategies without any additional configuration.

Expand All @@ -590,8 +590,8 @@ There are currently 2 examples for 2 clusters, that you can run sumalteniously.
NOTE: All properties files are preconfigured to work out of the box.

```
./cdc-start-up.sh --ignite ../examples/config/cdc-start-up/cluster-1
./cdc-start-up.sh --ignite ../examples/config/cdc-start-up/cluster-2
./cdc-start-up.sh --ignite cluster-1
./cdc-start-up.sh --ignite cluster-2
```

* Start CDC clients with specified properties:
Expand All @@ -606,19 +606,19 @@ NOTE: Start both clusters (as in previous example with Ignite nodes) before star

Here is an example on how to start Active-Passive inter-cluster communication with 2 separate nodes and one thin CDC client for Ignite-to-Ignite replication from cluster 1 to cluster 2 (Run the commands independently):
```
./cdc-start-up.sh --ignite ../examples/config/cdc-start-up/cluster-1
./cdc-start-up.sh --ignite ../examples/config/cdc-start-up/cluster-2
./cdc-start-up.sh --cdc-client --ignite-to-ignite-thin --activate-cluster ../examples/config/cdc-start-up/cluster-1
./cdc-start-up.sh --ignite cluster-1
./cdc-start-up.sh --ignite cluster-2
./cdc-start-up.sh --cdc-client --ignite-to-ignite-thin --activate-cluster cluster-1
```

NOTE: Make sure clusters fully started up before starting CDC client.

Here is an example on how to start Active-Active inter-cluster communication with 2 separate nodes and 2 CDC clients (thick) for Ignite-to-Ignite replication (Run the commands independently):
```
./cdc-start-up.sh --ignite ../examples/config/cdc-start-up/cluster-1
./cdc-start-up.sh --ignite ../examples/config/cdc-start-up/cluster-2
./cdc-start-up.sh --cdc-client --ignite-to-ignite --activate-cluster ../examples/config/cdc-start-up/cluster-1
./cdc-start-up.sh --cdc-client --ignite-to-ignite ../examples/config/cdc-start-up/cluster-2
./cdc-start-up.sh --ignite cluster-1
./cdc-start-up.sh --ignite cluster-2
./cdc-start-up.sh --cdc-client --ignite-to-ignite --activate-cluster cluster-1
./cdc-start-up.sh --cdc-client --ignite-to-ignite cluster-2
```

NOTE: To start CDC with Kafka you need to start topics beforehand.
Expand All @@ -641,10 +641,10 @@ We use the following topics naming for our examples:

Here is an example on how to start Active-Passive inter-cluster communication with 2 separate nodes and 2 CDC clients for replication with Kafka from cluster 1 to cluster 2 (Run the commands independently):
```
./cdc-start-up.sh --ignite ../examples/config/cdc-start-up/cluster-1
./cdc-start-up.sh --ignite ../examples/config/cdc-start-up/cluster-2
./cdc-start-up.sh --cdc-client --ignite-to-kafka --activate-cluster ../examples/config/cdc-start-up/cluster-1
./cdc-start-up.sh --cdc-client --kafka-to-ignite-thin ../examples/config/cdc-start-up/cluster-2
./cdc-start-up.sh --ignite cluster-1
./cdc-start-up.sh --ignite cluster-2
./cdc-start-up.sh --cdc-client --ignite-to-kafka --activate-cluster cluster-1
./cdc-start-up.sh --cdc-client --kafka-to-ignite-thin cluster-2
```

* You can check CDC replication with `--check-cdc`. Use it in parallel with Active-Passive/Active-Active replication. To start CDC check for proposed entry:
Expand Down

0 comments on commit 84a6d2e

Please sign in to comment.