You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(active-active): Child workflows should always use parent's active cluster policy (#7348)
<!-- Describe what has changed in this PR -->
**What changed?**
Update child workflow to use parent's active cluster selection policy
<!-- Tell your future self why have you made these changes -->
**Why?**
Child workflow should have the same active cluster selection policy as
parent workflow.
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
**How did you test it?**
Simulation tests
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
**Potential risks**
<!-- Is it notable for release? e.g. schema updates, configuration or
data migration required? If so, please mention it, and also update
CHANGELOG.md -->
**Release notes**
<!-- Is there any documentation updates should be made for config,
https://cadenceworkflow.io/docs/operation-guide/setup/ ? If so, please
open an PR in https://github.com/cadence-workflow/cadence-docs -->
**Documentation Changes**
# This file is used as dynamicconfig override for "activeactive" replication simulation scenario configured via simulation/replication/testdata/replication_simulation_activeactive.yaml
2
+
system.writeVisibilityStoreName:
3
+
- value: "db"
4
+
system.readVisibilityStoreName:
5
+
- value: "db"
6
+
history.replicatorTaskBatchSize:
7
+
- value: 25
8
+
constraints: {}
9
+
frontend.failoverCoolDown:
10
+
- value: 5s
11
+
history.ReplicationTaskProcessorStartWait: # default is 5s. repl task processor sleeps this much before processing received messages.
0 commit comments