All Products
Search

This Product

    PolarDB:ModifyDBCluster

    Document Center

    PolarDB:ModifyDBCluster

    Last Updated:Oct 18, 2024

    Modifies the configurations of a PolarDB for MySQL 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 cluster ID.

    Note You can call the DescribeDBClusters operation to query information about all PolarDB clusters that are deployed in a specified region, such as cluster IDs.
    		pc-*************
    StandbyHAModestringNo

    Specifies whether to enable cross-zone automatic switchover. Valid values:

    • ON: enables cross-zone automatic switchover.
    • OFF: disables cross-zone automatic switchover.
    		ON
    DataSyncModestringNo

    The method used to replicate data across zones. Valid values:

    • AsyncSync: the asynchronous mode.
    • SemiSync: the semi-synchronous mode.
    		AsynSync
    FaultSimulateModestringNo

    The level of the disaster recovery drill. Valid values:

    • 0 or FaultInjection: The primary zone level.
    • 1: The node level.
    Note

    • In primary zone-level disaster recovery drill scenarios, all compute nodes in the primary zone are unavailable. Data loss occurs during failovers in the scenarios.

    • In node-level disaster recovery drill scenarios, you can specify only one compute node for the disaster recovery drill. You can use the DBNodeCrashList parameter to specify the name of the compute node that you want to use for the drill.

    		0
    StorageAutoScalestringNo

    Specifies whether to enable automatic storage scaling. This parameter is available only for Standard Edition clusters. Valid values:

    • Enable
    • Disable
    		Enable
    CompressStoragestringNo

    Specifies whether to enable storage compression. Set the value to ON.

    		ON
    StorageUpperBoundlongNo

    The maximum storage capacity of the cluster of Standard Edition in automatic scaling. Unit: GB.

    Note The maximum value of this parameter is 32000.
    		800
    DBNodeCrashListstringNo

    The list of nodes for the drill.

    Note You can specify only one node for a node-level disaster recovery drill. For a primary zone-level disaster recovery drill, you can either choose not to specify this parameter or specify all nodes.
    		pi-rwxxx
    FaultInjectionTypestringNo

    The fault injection method. Valid values:

    • CrashSQLInjection: Crash SQL-based fault injection.
    		0

    You can specify only one of the following parameters: StandbyHAMode, DataSyncMode, FaultSimulateMode, and StorageAutoScale. For example, if you specify the StandbyHAMode parameter, you cannot specify another three parameters.

    Response parameters

    ParameterTypeDescriptionExample
    object

    Schema of Response

    RequestIdstring

    The request ID.

    		CD3FA5F3-FAF3-44CA-AFFF-BAF869******
    DBClusterIdstring

    The cluster ID.

    		pc-*************
    OrderIdstring

    The order ID.

    		2148126708*****

    Examples

    Sample success responses

    JSONformat

    {
  "RequestId": "CD3FA5F3-FAF3-44CA-AFFF-BAF869******",
  "DBClusterId": "pc-*************",
  "OrderId": "2148126708*****"
}

    Error codes

    HTTP status codeError codeError messageDescription
    400OperationDenied.CreateDBNodesWithStrictConsistencyOn3AZ cluster does not allow create db nodes.Nodes cannot be added for multi-zone clusters.
    400InvalidDBProxyClusterClass.MalformedThe specified parameter DBProxyClusterClass is not valid.The specified DBProxyClusterClass parameter is invalid.
    400InvalidDBNodeNum.MalformedThe number of parameter DBNode.N is not valid.The specified number of database nodes is invalid.
    400OperationDenied.ModifyDBNodeClassWithStrictConsistencyOn3AZ cluster does not allow modify db node class.The specification of the Logger node cannot be changed for multi-zone clusters.
    400InvalidDowngradeDBNodeClass.LimitThe specified Downgrade DBNodeClass is limit on the MaxDiskSize.The downgrade of DBNodeClass is limited by the MaxDiskSize parameter.
    400InvalidEngine.UnsupportedThe specified Engine does not support this feature.This feature is not supported by the specified engine.
    400OperationDenied.ModifyProxyWithStrictConsistencyOn3AZ cluster does not allow modify proxy.The PolarProxy node cannot be changed for multi-zone clusters.
    400StandbyClusterTurnOnThe specified dbCluster already turn on hot standby cluster.Hot standby clusters are enabled for the specified dbCluster.
    403IncorrectDBInstanceTypeCurrent DB instance type does not support this operation.-
    403IncorrectDBInstanceCurrent DB instance does not support this operation.The current DB instance does not support this operation
    403OperationDenied.LockModeThe operation is not permitted due to lock of cluster.The PolarDB cluster is locked and does not support this operation.
    403OperationDenied.DBClusterStatusThe operation is not permitted due to status of cluster.The PolarDB cluster does not support this operation in the current state.
    403OperationDenied.TempUpgradeDuringThis operation is not allowed during the temporary upgrade of the cluster.This operation cannot be performed during the temporary upgrade of the cluster.
    403InvalidParam.PgDBNodeSpecThe specification PGO of DB nodes is incorrect.The PGO in the specification of the database cluster is incorrect.
    403InvalidParam.NoChangeNo change foundNo changes are detected.
    403OperationDenied.DBNodeClassThe target DB node class is invalid for SQL acceleration.The class of the target database node cannot be used for SQL acceleration.
    403OperationDenied.ReaderNumThe target reader node number is invalid for SQL acceleration.The number of the target reader node cannot be used for SQL acceleration.
    403InvalidParam.DBNodeNumThe number of DB nodes is incorrect.The number of database nodes is incorrect.
    403OperationDenied.DBNodeRoleThe operation is not permitted due to the role of node.This operation is not supported by the node role.
    403OperationDenied.DeleteNodeThe senormal version cluster does not allow the deletion of ro nodes and standby nodes at the same time.In clusters of the senormal version, the read-only node and standby node cannot be deleted at the same time.
    403OperationDenied.EndpointDBNodeNumberThe operation is not permitted due to node number for Endpoint.This operation is not supported by the endpoint.
    403OperationDenied.StandbyEqualSpecThe spec of standby must be equal to rwThe specification of the standby node must be rw.
    403OperationDenied.DeleteDBNodeNumberThe operation is not permitted due to the node number to delete.This node cannot be deleted.
    403OperationDenied.DbVersionThe operation is not permitted due to DbVersion.This operation is not supported by the database version.
    403OperationDenied.ClusterCategoryThe operation is not permitted due to cluster category.This series is not supported by the cluster.
    403OperationDenied.clusterSingleNodeLimitSingle-node instances are not supported and need to be upgraded to cluster versionSingle-node instances are not supported. You must upgrade them to the Cluster Edition.
    403InvalidParam.CRACParamNodeNumThe CRAC nodes cannot exceed 8.The number of CRAC nodes cannot exceed eight.
    403InvalidParam.ECSESSDSTANDARDParamNodeNumThe ECSESSDSTANDARD nodes cannot exceed 8.The number of ECESSDSTANDARD nodes cannot exceed eight.
    404InvalidParamInvalid Parameter.-
    404InvalidEditTypeWrong upgrade type.The upgrade type is incorrect.
    500InternalErrorThe request processing has failed due to some unknown error, exception or failure.The request failed to be processed because unknown errors, exceptions, or failures have occurred.

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

    Change history

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