switchover_global_cluster
async
¶
switchover_global_cluster(
*,
config_overrides: Optional[AsyncRDSClientConfig] = None,
global_cluster_identifier: Optional[GlobalClusterIdentifier] = None,
target_db_cluster_identifier: Optional[DBClusterIdentifier] = None,
) -> SwitchoverGlobalClusterResult
Switches over the specified secondary DB cluster to be the new primary DB cluster in the global database cluster. Switchover operations were previously called "managed planned failovers."
Aurora promotes the specified secondary cluster to assume full read/write capabilities and demotes the current primary cluster to a secondary (read-only) cluster, maintaining the orginal replication topology. All secondary clusters are synchronized with the primary at the beginning of the process so the new primary continues operations for the Aurora global database without losing any data. Your database is unavailable for a short time while the primary and selected secondary clusters are assuming their new roles. For more information about switching over an Aurora global database, see Performing switchovers for Amazon Aurora global databases in the Amazon Aurora User Guide.
This operation is intended for controlled environments, for operations such as "regional rotation" or to fall back to the original primary after a global database failover.
Parameters:
-
global_cluster_identifier(Optional[GlobalClusterIdentifier], default:None) –The identifier of the global database cluster to switch over. This parameter isn't case-sensitive.
Constraints:
-
Must match the identifier of an existing global database cluster (Aurora global database).
-
-
target_db_cluster_identifier(Optional[DBClusterIdentifier], default:None) –The identifier of the secondary Aurora DB cluster to promote to the new primary for the global database cluster. Use the Amazon Resource Name (ARN) for the identifier so that Aurora can locate the cluster in its Amazon Web Services Region.
Raises:
-
DBClusterNotFoundFault–DBClusterIdentifierdoesn't refer to an existing DB cluster. -
GlobalClusterNotFoundFault–The
GlobalClusterIdentifierdoesn't refer to an existing global database cluster. -
InvalidDBClusterStateFault–The requested operation can't be performed while the cluster is in this state.
-
InvalidGlobalClusterStateFault–The global cluster is in an invalid state and can't perform the requested operation.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_rds/_services/async_rds.py
15989 15990 15991 15992 15993 15994 15995 15996 15997 15998 15999 16000 16001 16002 16003 16004 16005 16006 16007 16008 16009 16010 16011 16012 16013 16014 16015 16016 16017 16018 16019 16020 16021 16022 16023 16024 16025 16026 16027 16028 16029 16030 16031 16032 16033 16034 16035 16036 16037 16038 16039 16040 16041 16042 16043 16044 16045 16046 | |