Skip to content

Commit e5ed7f7

Browse files
Feature/adding canary for cross cluster -> readme patch (#4870)
* Adds cross-cluster canary * updating readme
1 parent 608bcb5 commit e5ed7f7

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

canary/README.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -265,3 +265,21 @@ To manually start one run of this test case:
265265
```
266266
cadence --do <> workflow start --tl canary-task-queue --et 10 --wt workflow.batch -i 0
267267
```
268+
269+
### Cross Cluster
270+
271+
Executes the 'cross-cluster' feature which allows child workflows to be launched in different clusters and different domains. The test itself will launch a workflow in a domain equivalent to the current canary domain suffixed with `-cross-cluster` (and self-register it as necessary).
272+
273+
This test case is launched by the 'sanity' cron workflow if enabled.
274+
275+
To enable this feature, its necessary to enable it in config with the
276+
`crossClusterTestMode` config key set to `test-all`. Eg:
277+
278+
```yaml
279+
canary:
280+
domains: ["cadence-canary"]
281+
crossClusterTestMode: "test-all"
282+
canaryDomainClusters: ["cluster0", "cluster1", "cluster2"]
283+
```
284+
285+
The canary test will fail the target domain over to a different cluster and back again with some small probability each iteration. This ensures that both the cross-domain and the cross-cluster parts are excercised.

0 commit comments

Comments
 (0)