-
Notifications
You must be signed in to change notification settings - Fork 867
Test active-active behavior with concurrent SignalWithStart requests #7270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…the query_workflow step to correctly retrieve signals, cleaning up some of the configuration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not enabled in CI. Could you add it to https://github.com/cadence-workflow/cadence/blob/master/.github/workflows/replication-simulation.yml?
...tion/replication/testdata/replication_simulation_activeactive_same_wfid_signalwithstart.yaml
Show resolved
Hide resolved
| # This file is a replication simulation scenario spec. | ||
| # It is parsed into ReplicationSimulationConfig struct. | ||
| # Replication simulation for this file can be run via ./simulation/replication/run.sh activeactive_same_wfid_signalwithstart_delayed | ||
| # Dynamic config overrides can be set via config/dynamicconfig/replication_simulation_activeactive_same_wfid_signalwithstart_delayed.yml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this dynamic config file is not created
What changed?
Tests conflict resolution when the same workflowID is used to create workflows in two different clusters with an Active-Active setup in the domain.
Why?
Cadence does not support two workflows existing with the same workflow ID. When a domain is configured active-active it can be possible for a user to make two simultaneous requests to two different clusters with the same workflow ID. When this happens, both workflows will run temporarily until the clusters have replicated their data to the other, at which point the conflict will have to be resolved.
This test is a follow up to #7265, testing the scenario when SignalWithStart is used (rather than StartWorkflow).
How did you test it?
Locally + against dev canary domains.
Potential risks
N/A
Release notes
N/A
Documentation Changes
N/A