docs
api
Load Balance(ULB)
ReleaseBackend

Release the backend instances of the traditional load balancer - ReleaseBackend

Overview

Release backend resource instances from CLB's VServer

ℹ️ When VServer is at Layer 7, the backend instance must be removed from the forwarding rules before it can be released. BackendId corresponds to the BackendId returned by AllocateBackend or the BackendId in ULBBackendSet returned by DescribeULB/DescribeVServer, which is the node Id of the traditional load balancing service.

Definition

Public Parameters

Parameter NameTypeDescription InformationRequired
ActionstringCorresponding API command name, the current API is ReleaseBackend.Yes
PublicKeystringThe user's public key can be obtained from Console (opens in a new tab)Yes
SignaturestringUser signature generated based on public key and API command, see Signature AlgorithmYes

Request Parameters

Parameter NameTypeDescription InformationRequired
RegionstringRegion. See List of Regions and Availability ZonesYes
ProjectIdstringProject ID. If not filled in, the default project is used, sub-accounts must be filled in. Please refer to the GetProjectList interface.Yes
ULBIdstringID of the traditional load balancing instanceYes
BackendIdstringID of the backend resource instance (CLB backend ID, not the resource's own ID)Yes

Response Field

Field NameTypeDescription InformationRequired
RetCodeintReturn status code. If it is 0, it means successful return. If it is not 0, it means failure.Yes
ActionstringOperation command name.Yes
MessagestringReturns an error message, providing detailed description when RetCode is non-zero.No

Example

Request Example

https://api.surfercloud.com/?Action=ReleaseBackend
&Region=cn-bj2
&ProjectId=project-XXXX
&ULBId=ulb-XXXX
&BackendId=backend-XXXX

Response Example

{
  "Action": "ReleaseBackendResponse",
  "RetCode": 0
}
  • Company
  • ContactUs
  • Blog
Copyright © 2024 SurferCloud All Rights Reserved