Binding and Unbinding a Queue
Constraints
- The CIDR block of the DLI queue that is bound with a datasource connection cannot overlap with that of the data source.
- The default queue cannot be bound with a connection.
Binding a Queue
Before using an enhanced datasource connection, you must bind a queue and ensure that the VPC peering connection is in the Active state.
Viewing Details about a Bound Queue
Parameter |
Description |
---|---|
VPC Peering ID |
ID of the VPC peering connection created in the cluster to which the queue belongs.
NOTE:
A VPC peering connection is created for each queue bound to an enhanced datasource connection. The VPC peering connection is used for cross-VPC communication. Ensure that the security group used by the data source allows access from the DLI queue CIDR block, and do not delete the VPC peering connection during the datasource connection. |
Name |
Name of a bound queue. |
Connection Status |
Datasource connection status. The following three statuses are available:
NOTE:
If the connection status is Failed, click on the left to view the detailed error information. |
Updated |
Time when a connection is updated. The connections in the connection list can be displayed according to the update time in ascending or descending order. |
Operation |
Unbind Queue: This operation is used to unbind a datasource connection from a queue. |
Unbinding a Queue
If you do not need to use an enhanced datasource connection, you can unbind the queue from it to release resources.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.