Work Requests for Network Load Balancers
Generate information on each network load balancer operation's work requests.
Many of the network load balancer requests do not take effect immediately. In these cases, the request spawns an asynchronous workflow for fulfillment.
To provide visibility for in-progress workflows, the network load balancer creates a work request object. Because some operations depend on the completion of other operations, you must monitor each operation's work request and confirm it has succeeded before proceeding to the next operation. For example, if you want to create a backend set and add a backend server to the new set, you first must create the backend set. After that operation completes, you can add the backend server.
If you try to add a backend server before the backend set creation completes, the system cannot ensure that the request to add the server succeeds. You can monitor the request to add a backend set to determine when that workflow is complete, and then add the backend server.
You can perform the following work request management tasks:
Work Request States
The work request states are:
- ACCEPTED
- The request is in the work request queue to be processed.
- IN PROGRESS
- A work request record exists for the specified request, but no associated WORK_COMPLETED record is present.
- SUCCEEDED
- A work request record exists for this request and an associated WORK_COMPLETED record has the state SUCCEEDED.
- FAILED
- A work request record exists for this request and an associated WORK_COMPLETED record has the state FAILED.
The network load balancer does not use the common Work Requests API to support work request operations. Instead, the API supports network load balancer work requests.