All Products
Search
Document Center

PolarDB:FailoverDBCluster

Last Updated:Oct 17, 2024

Performs a manual failover to promote a read-only node to the primary node in a PolarDB cluster.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

ParameterTypeRequiredDescriptionExample
DBClusterIdstringYes

The ID of the cluster.

pc-**************
TargetDBNodeIdstringNo

The ID of the read-only node that you want to promote to the primary node. You can call the DescribeDBClusters operation to query node information, such as node IDs.

Note
  • If you leave this parameter empty, the system selects one or more available read-only nodes that have the highest failover priority as candidate primary nodes. If the failover to the first read-only node fails due to network issues, abnormal replication status, or other reasons, the system attempts to fail over your applications to the next read-only node until the failover is successful.
  • This parameter is required for PolarDB for Oracle and PolarDB for PostgreSQL clusters. This parameter is optional for PolarDB for MySQL clusters.
  • pi-***********
    RollBackForDisasterbooleanNo

    Specifies whether to switch back services to the original primary zone when the original primary zone recovers.

    • true
    • false
    false
    ClientTokenstringNo

    The client token that is used to ensure the idempotence of the request. You can use the client to generate the value, but you must make sure that it is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length. The token is case-sensitive.

    6000170000591aed949d0f54a343f1a4233c1e7d1c5******
    TargetZoneTypestringNo

    Whether it is a primary-standby switch within the primary availability zone, with the following values:

    Primary: Primary-standby switch within the primary availability zone. Standby: Switch to the storage hot backup cluster.

    Primary

    Response parameters

    ParameterTypeDescriptionExample
    object
    RequestIdstring

    The ID of the request.

    D0CEC6AC-7760-409A-A0D5-E6CD86******

    Examples

    Sample success responses

    JSONformat

    {
      "RequestId": "D0CEC6AC-7760-409A-A0D5-E6CD86******"
    }

    Error codes

    HTTP status codeError codeError messageDescription
    400HaStatusNotSupportCurrent DB instance HA status does not support this operation.The HA status of the instance does not support this operation.
    400InvalidDBNodeId.MalformedThe specified parameter DBNodeId is not valid.The specified DBNodeId parameter is invalid.
    400InvalidDBType.MalformedThe Specified DBType is not valid.The specified database type is invalid.
    400UnsupportHighFrequenceSwitchOverThe instance has switch over too frequent within ten minutes.The current switch is too frequent, it is recommended to try again in 5 minutes.
    400UnsupportWitchUnhealthyReplicationThe action is unsupported with unhealthy replication.The current replication relationship is abnormal. Switching is not supported.
    403OperationDenied.DBNodeTypeThe operation is not permitted due to type of node.The specified node type does not support this operation.
    403OperationDenied.ClusterCategoryThe operation is not permitted due to cluster category.This series is not supported by the cluster.
    404InvalidDBCluster.NotFoundThe DBClusterId provided does not exist in our records.The specified DBClusterId parameter does not exist in the current record.
    404InvalidDBClusterId.MalformedThe specified parameter DBClusterId is not valid.The specified DBClusterId parameter is invalid.

    For a list of error codes, visit the Service error codes.

    Change history

    Change timeSummary of changesOperation
    2024-08-20The Error code has changedView Change Details
    2024-08-08The Error code has changed. The request parameters of the API has changedView Change Details
    2023-12-07The Error code has changed. The request parameters of the API has changedView Change Details
    2023-09-12The Error code has changedView Change Details
    2023-06-12The Error code has changedView Change Details
    2022-06-10The Error code has changedView Change Details