834ef79509
The content was moved over from the Keycloak Benchmark subproject. Closes #24844 Signed-off-by: Alexander Schwartz <aschwart@redhat.com> Co-authored-by: Pedro Ruivo <pruivo@redhat.com> Co-authored-by: Michal Hajas <mhajas@redhat.com> Co-authored-by: Kamesh Akella <kakella@redhat.com> Co-authored-by: Ryan Emerson <remerson@redhat.com> Co-authored-by: Anna Manukyan <amanukya@redhat.com> Co-authored-by: Thomas Darimont <thomas.darimont@googlemail.com> Co-authored-by: Stian Thorgersen <stian@redhat.com> Co-authored-by: Thomas Darimont <thomas.darimont@googlemail.com> Co-authored-by: AndyMunro <amunro@redhat.com>
15 lines
856 B
Text
15 lines
856 B
Text
Assuming a Regional multi-AZ Aurora deployment, the current writer instance should be in the same region as the active {project_name} cluster to avoid latencies and communication across availability zones.
|
|
|
|
Switching the writer instance of Aurora will lead to a short downtime. The writer instance in the other site with a slightly longer latency might be acceptable for some deployments.
|
|
Therefore, this situation might be deferred to a maintenance window or skipped depending on the circumstances of the deployment.
|
|
|
|
To change the writer instance, run a failover.
|
|
This change will make the database unavailable for a short time.
|
|
{project_name} will need to re-establish database connections.
|
|
|
|
To fail over the writer instance to the other AZ, issue the following command:
|
|
|
|
[source,bash]
|
|
----
|
|
aws rds failover-db-cluster --db-cluster-identifier ...
|
|
----
|