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
We have support to initialize the target sequences during the swtiching of PRIMARY (write) traffic. But in dry run mode these commands seem not to be executed.
2 reasons why I believe this would be useful:
I've run into a situation where the initialize-target-sequences took longer than the allowed time (default 15sec) and the SwitchTraffic failed because of this. This wasn't caught in dry-run mode.
While dry-run would execute all the steps to check the sequences verify the work it would need to do to figure out if updates are needed (just not the actual updating), we could use the dry-run output as some sort of a fail-safe mechanism in specific use-cases where initialize-target-sequences might not be 100% safe to execute (think busy systems with multi-tenant migrations running)
Use Case(s)
see description
The text was updated successfully, but these errors were encountered:
Feature Description
We have support to initialize the target sequences during the swtiching of PRIMARY (write) traffic. But in dry run mode these commands seem not to be executed.
2 reasons why I believe this would be useful:
initialize-target-sequences
took longer than the allowed time (default 15sec) and the SwitchTraffic failed because of this. This wasn't caught indry-run
mode.dry-run
would execute all the steps to check the sequences verify the work it would need to do to figure out if updates are needed (just not the actual updating), we could use thedry-run
output as some sort of a fail-safe mechanism in specific use-cases whereinitialize-target-sequences
might not be 100% safe to execute (think busy systems with multi-tenant migrations running)Use Case(s)
see description
The text was updated successfully, but these errors were encountered: