API behavior and statuses¶
The Load Balancer API is considered to be asynchronous because mutable operations (that is, POST, PUT, and DELETE) are often queued up and then handled accordingly. All successful asynchronous API operations have a normal response code of 202.
The load balancer
status attribute is closely linked to mutable operations
because it is updated depending on the operation or the state of the load
balancer. The following table lists the possible load balancer statuses.
|ACTIVE||The load balancer is active.|
|ERROR||The load balancer is in an error state.|
|PENDING_CREATE||The load balancer has a create action pending.|
|PENDING_DELETE||The load balancer has a delete action pending.|
|PENDING_UPDATE||The load balancer has an update action pending.|
There is not currently a DELETED status. If you use the API to request
details about a deleted object, you receive a
404 Not Found response.
Any load balancer can have only one mutable operation requested at a time. If concurrent mutable requests are issued for a load balancer, only one of the requests is accepted. Issuing concurrent nonmutable requests (GET) is allowed.
To determine when a mutable operation is completed, poll the load balancer
details once every 5 to 10 seconds to determine if the load balancer has
changed back to an
ACTIVE status. When the load balancer is back in the
ACTIVE status, another mutable operation can be accepted.