All Downloads are FREE. Search and download functionalities are using the official Maven repository.

com.tencentcloudapi.postgres.v20170312.models.ModifyDBInstanceHAConfigRequest Maven / Gradle / Ivy

/*
 * Copyright (c) 2017-2018 THL A29 Limited, a Tencent company. All Rights Reserved.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *    http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package com.tencentcloudapi.postgres.v20170312.models;

import com.tencentcloudapi.common.AbstractModel;
import com.tencentcloudapi.common.SSEResponseModel;
import com.google.gson.annotations.SerializedName;
import com.google.gson.annotations.Expose;
import java.util.HashMap;

public class ModifyDBInstanceHAConfigRequest extends AbstractModel {

    /**
    * Instance ID
    */
    @SerializedName("DBInstanceId")
    @Expose
    private String DBInstanceId;

    /**
    * Primary-standby sync mode. Valid values:
  • `Semi-sync`
  • `Async` */ @SerializedName("SyncMode") @Expose private String SyncMode; /** * Maximum data lag for high-availability standby server. The standby node can be promoted to the primary node when its data lag and the delay time are both less than the value of `MaxStandbyLatency` and `MaxStandbyLag` respectively.
  • Unit: byte
  • Value range: 1073741824-322122547200 */ @SerializedName("MaxStandbyLatency") @Expose private Long MaxStandbyLatency; /** * The maximum delay for high-availability standby server The standby node can be promoted to the primary node when its data lag and the delay time are both less or equals to the value of `MaxStandbyLatency` and `MaxStandbyLag` respectively.
  • Unit: s
  • Value range: 5-10 */ @SerializedName("MaxStandbyLag") @Expose private Long MaxStandbyLag; /** * Maximum data sync lag for standby server. If data lag of the standby node and the delay ime are both less than or equals to the values of `MaxSyncStandbyLatency` and `MaxSyncStandbyLag`, the standby server adopts semi-sync replication; if not, it adopts async replication. This value is only valid for the instance with `SyncMode` set to `Semi-sync`. When the semi-sync replication mode of the instance is not allowed to downgrade to async replication, `MaxSyncStandbyLatency` and `MaxSyncStandbyLag` are not required. When the semi-sync instance is allowed to downgrade to async replication, `MaxSyncStandbyLatency` is required and `MaxSyncStandbyLag` must be left empty for PostgreSQL 9; `MaxSyncStandbyLatency` and MaxSyncStandbyLag` are required for PostgreSQL 10 and later. */ @SerializedName("MaxSyncStandbyLatency") @Expose private Long MaxSyncStandbyLatency; /** * Maximum delay for sync standby server. If the delay time for standby server and the data lag are both less than or equals to the value of `MaxSyncStandbyLag` and `MaxSyncStandbyLatency` respectively, the standby server adopts sync replication mode; if not, it adopts async replication. This value is only valid for the instance with `SyncMode` set to `Semi-sync`. When the semi-sync replication mode of the instance is not allowed to downgrade to async replication, `MaxSyncStandbyLatency` and `MaxSyncStandbyLag` are not required. When the semi-sync instance is allowed to downgrade to async replication, `MaxSyncStandbyLatency` is required and `MaxSyncStandbyLag` must be left empty for PostgreSQL 9; `MaxSyncStandbyLatency` and MaxSyncStandbyLag` are required for PostgreSQL 10 and later. */ @SerializedName("MaxSyncStandbyLag") @Expose private Long MaxSyncStandbyLag; /** * Get Instance ID * @return DBInstanceId Instance ID */ public String getDBInstanceId() { return this.DBInstanceId; } /** * Set Instance ID * @param DBInstanceId Instance ID */ public void setDBInstanceId(String DBInstanceId) { this.DBInstanceId = DBInstanceId; } /** * Get Primary-standby sync mode. Valid values:
  • `Semi-sync`
  • `Async` * @return SyncMode Primary-standby sync mode. Valid values:
  • `Semi-sync`
  • `Async` */ public String getSyncMode() { return this.SyncMode; } /** * Set Primary-standby sync mode. Valid values:
  • `Semi-sync`
  • `Async` * @param SyncMode Primary-standby sync mode. Valid values:
  • `Semi-sync`
  • `Async` */ public void setSyncMode(String SyncMode) { this.SyncMode = SyncMode; } /** * Get Maximum data lag for high-availability standby server. The standby node can be promoted to the primary node when its data lag and the delay time are both less than the value of `MaxStandbyLatency` and `MaxStandbyLag` respectively.
  • Unit: byte
  • Value range: 1073741824-322122547200 * @return MaxStandbyLatency Maximum data lag for high-availability standby server. The standby node can be promoted to the primary node when its data lag and the delay time are both less than the value of `MaxStandbyLatency` and `MaxStandbyLag` respectively.
  • Unit: byte
  • Value range: 1073741824-322122547200 */ public Long getMaxStandbyLatency() { return this.MaxStandbyLatency; } /** * Set Maximum data lag for high-availability standby server. The standby node can be promoted to the primary node when its data lag and the delay time are both less than the value of `MaxStandbyLatency` and `MaxStandbyLag` respectively.
  • Unit: byte
  • Value range: 1073741824-322122547200 * @param MaxStandbyLatency Maximum data lag for high-availability standby server. The standby node can be promoted to the primary node when its data lag and the delay time are both less than the value of `MaxStandbyLatency` and `MaxStandbyLag` respectively.
  • Unit: byte
  • Value range: 1073741824-322122547200 */ public void setMaxStandbyLatency(Long MaxStandbyLatency) { this.MaxStandbyLatency = MaxStandbyLatency; } /** * Get The maximum delay for high-availability standby server The standby node can be promoted to the primary node when its data lag and the delay time are both less or equals to the value of `MaxStandbyLatency` and `MaxStandbyLag` respectively.
  • Unit: s
  • Value range: 5-10 * @return MaxStandbyLag The maximum delay for high-availability standby server The standby node can be promoted to the primary node when its data lag and the delay time are both less or equals to the value of `MaxStandbyLatency` and `MaxStandbyLag` respectively.
  • Unit: s
  • Value range: 5-10 */ public Long getMaxStandbyLag() { return this.MaxStandbyLag; } /** * Set The maximum delay for high-availability standby server The standby node can be promoted to the primary node when its data lag and the delay time are both less or equals to the value of `MaxStandbyLatency` and `MaxStandbyLag` respectively.
  • Unit: s
  • Value range: 5-10 * @param MaxStandbyLag The maximum delay for high-availability standby server The standby node can be promoted to the primary node when its data lag and the delay time are both less or equals to the value of `MaxStandbyLatency` and `MaxStandbyLag` respectively.
  • Unit: s
  • Value range: 5-10 */ public void setMaxStandbyLag(Long MaxStandbyLag) { this.MaxStandbyLag = MaxStandbyLag; } /** * Get Maximum data sync lag for standby server. If data lag of the standby node and the delay ime are both less than or equals to the values of `MaxSyncStandbyLatency` and `MaxSyncStandbyLag`, the standby server adopts semi-sync replication; if not, it adopts async replication. This value is only valid for the instance with `SyncMode` set to `Semi-sync`. When the semi-sync replication mode of the instance is not allowed to downgrade to async replication, `MaxSyncStandbyLatency` and `MaxSyncStandbyLag` are not required. When the semi-sync instance is allowed to downgrade to async replication, `MaxSyncStandbyLatency` is required and `MaxSyncStandbyLag` must be left empty for PostgreSQL 9; `MaxSyncStandbyLatency` and MaxSyncStandbyLag` are required for PostgreSQL 10 and later. * @return MaxSyncStandbyLatency Maximum data sync lag for standby server. If data lag of the standby node and the delay ime are both less than or equals to the values of `MaxSyncStandbyLatency` and `MaxSyncStandbyLag`, the standby server adopts semi-sync replication; if not, it adopts async replication. This value is only valid for the instance with `SyncMode` set to `Semi-sync`. When the semi-sync replication mode of the instance is not allowed to downgrade to async replication, `MaxSyncStandbyLatency` and `MaxSyncStandbyLag` are not required. When the semi-sync instance is allowed to downgrade to async replication, `MaxSyncStandbyLatency` is required and `MaxSyncStandbyLag` must be left empty for PostgreSQL 9; `MaxSyncStandbyLatency` and MaxSyncStandbyLag` are required for PostgreSQL 10 and later. */ public Long getMaxSyncStandbyLatency() { return this.MaxSyncStandbyLatency; } /** * Set Maximum data sync lag for standby server. If data lag of the standby node and the delay ime are both less than or equals to the values of `MaxSyncStandbyLatency` and `MaxSyncStandbyLag`, the standby server adopts semi-sync replication; if not, it adopts async replication. This value is only valid for the instance with `SyncMode` set to `Semi-sync`. When the semi-sync replication mode of the instance is not allowed to downgrade to async replication, `MaxSyncStandbyLatency` and `MaxSyncStandbyLag` are not required. When the semi-sync instance is allowed to downgrade to async replication, `MaxSyncStandbyLatency` is required and `MaxSyncStandbyLag` must be left empty for PostgreSQL 9; `MaxSyncStandbyLatency` and MaxSyncStandbyLag` are required for PostgreSQL 10 and later. * @param MaxSyncStandbyLatency Maximum data sync lag for standby server. If data lag of the standby node and the delay ime are both less than or equals to the values of `MaxSyncStandbyLatency` and `MaxSyncStandbyLag`, the standby server adopts semi-sync replication; if not, it adopts async replication. This value is only valid for the instance with `SyncMode` set to `Semi-sync`. When the semi-sync replication mode of the instance is not allowed to downgrade to async replication, `MaxSyncStandbyLatency` and `MaxSyncStandbyLag` are not required. When the semi-sync instance is allowed to downgrade to async replication, `MaxSyncStandbyLatency` is required and `MaxSyncStandbyLag` must be left empty for PostgreSQL 9; `MaxSyncStandbyLatency` and MaxSyncStandbyLag` are required for PostgreSQL 10 and later. */ public void setMaxSyncStandbyLatency(Long MaxSyncStandbyLatency) { this.MaxSyncStandbyLatency = MaxSyncStandbyLatency; } /** * Get Maximum delay for sync standby server. If the delay time for standby server and the data lag are both less than or equals to the value of `MaxSyncStandbyLag` and `MaxSyncStandbyLatency` respectively, the standby server adopts sync replication mode; if not, it adopts async replication. This value is only valid for the instance with `SyncMode` set to `Semi-sync`. When the semi-sync replication mode of the instance is not allowed to downgrade to async replication, `MaxSyncStandbyLatency` and `MaxSyncStandbyLag` are not required. When the semi-sync instance is allowed to downgrade to async replication, `MaxSyncStandbyLatency` is required and `MaxSyncStandbyLag` must be left empty for PostgreSQL 9; `MaxSyncStandbyLatency` and MaxSyncStandbyLag` are required for PostgreSQL 10 and later. * @return MaxSyncStandbyLag Maximum delay for sync standby server. If the delay time for standby server and the data lag are both less than or equals to the value of `MaxSyncStandbyLag` and `MaxSyncStandbyLatency` respectively, the standby server adopts sync replication mode; if not, it adopts async replication. This value is only valid for the instance with `SyncMode` set to `Semi-sync`. When the semi-sync replication mode of the instance is not allowed to downgrade to async replication, `MaxSyncStandbyLatency` and `MaxSyncStandbyLag` are not required. When the semi-sync instance is allowed to downgrade to async replication, `MaxSyncStandbyLatency` is required and `MaxSyncStandbyLag` must be left empty for PostgreSQL 9; `MaxSyncStandbyLatency` and MaxSyncStandbyLag` are required for PostgreSQL 10 and later. */ public Long getMaxSyncStandbyLag() { return this.MaxSyncStandbyLag; } /** * Set Maximum delay for sync standby server. If the delay time for standby server and the data lag are both less than or equals to the value of `MaxSyncStandbyLag` and `MaxSyncStandbyLatency` respectively, the standby server adopts sync replication mode; if not, it adopts async replication. This value is only valid for the instance with `SyncMode` set to `Semi-sync`. When the semi-sync replication mode of the instance is not allowed to downgrade to async replication, `MaxSyncStandbyLatency` and `MaxSyncStandbyLag` are not required. When the semi-sync instance is allowed to downgrade to async replication, `MaxSyncStandbyLatency` is required and `MaxSyncStandbyLag` must be left empty for PostgreSQL 9; `MaxSyncStandbyLatency` and MaxSyncStandbyLag` are required for PostgreSQL 10 and later. * @param MaxSyncStandbyLag Maximum delay for sync standby server. If the delay time for standby server and the data lag are both less than or equals to the value of `MaxSyncStandbyLag` and `MaxSyncStandbyLatency` respectively, the standby server adopts sync replication mode; if not, it adopts async replication. This value is only valid for the instance with `SyncMode` set to `Semi-sync`. When the semi-sync replication mode of the instance is not allowed to downgrade to async replication, `MaxSyncStandbyLatency` and `MaxSyncStandbyLag` are not required. When the semi-sync instance is allowed to downgrade to async replication, `MaxSyncStandbyLatency` is required and `MaxSyncStandbyLag` must be left empty for PostgreSQL 9; `MaxSyncStandbyLatency` and MaxSyncStandbyLag` are required for PostgreSQL 10 and later. */ public void setMaxSyncStandbyLag(Long MaxSyncStandbyLag) { this.MaxSyncStandbyLag = MaxSyncStandbyLag; } public ModifyDBInstanceHAConfigRequest() { } /** * NOTE: Any ambiguous key set via .set("AnyKey", "value") will be a shallow copy, * and any explicit key, i.e Foo, set via .setFoo("value") will be a deep copy. */ public ModifyDBInstanceHAConfigRequest(ModifyDBInstanceHAConfigRequest source) { if (source.DBInstanceId != null) { this.DBInstanceId = new String(source.DBInstanceId); } if (source.SyncMode != null) { this.SyncMode = new String(source.SyncMode); } if (source.MaxStandbyLatency != null) { this.MaxStandbyLatency = new Long(source.MaxStandbyLatency); } if (source.MaxStandbyLag != null) { this.MaxStandbyLag = new Long(source.MaxStandbyLag); } if (source.MaxSyncStandbyLatency != null) { this.MaxSyncStandbyLatency = new Long(source.MaxSyncStandbyLatency); } if (source.MaxSyncStandbyLag != null) { this.MaxSyncStandbyLag = new Long(source.MaxSyncStandbyLag); } } /** * Internal implementation, normal users should not use it. */ public void toMap(HashMap map, String prefix) { this.setParamSimple(map, prefix + "DBInstanceId", this.DBInstanceId); this.setParamSimple(map, prefix + "SyncMode", this.SyncMode); this.setParamSimple(map, prefix + "MaxStandbyLatency", this.MaxStandbyLatency); this.setParamSimple(map, prefix + "MaxStandbyLag", this.MaxStandbyLag); this.setParamSimple(map, prefix + "MaxSyncStandbyLatency", this.MaxSyncStandbyLatency); this.setParamSimple(map, prefix + "MaxSyncStandbyLag", this.MaxSyncStandbyLag); } }




  • © 2015 - 2025 Weber Informatics LLC | Privacy Policy