Help Center/ Data Lake Insight/ User Guide/ Data Migration and Transmission/ Configuring DLI to Read and Write Data from and to External Data Sources/ Managing Enhanced Datasource Connections/ Binding an Enhanced Datasource Connection to an Elastic Resource Pool
Updated on 2024-11-08 GMT+08:00
View PDF
Share

Binding an Enhanced Datasource Connection to an Elastic Resource Pool

Scenario

To connect other resource pools to data sources through enhanced datasource connections, bind enhanced datasource connections to resource pools on the Enhanced tab page.

Constraints

  • Enhanced datasource connections support only dedicated pay-per-use resource pools and queues.
  • The CIDR block of the DLI queue to be bound with a datasource connection cannot overlap with that of the data source.
  • The default queue preset in the system cannot be bound with a datasource connection.

Procedure

  1. Log in to the DLI management console.
  2. In the left navigation pane, choose Datasource Connections.
  3. On the Enhanced tab page displayed, bind an enhanced datasource connection to an elastic resource pool:
    1. Locate your desired enhanced datasource connection, click More in the Operation column, and select Bind Resource Pool.
    2. In the Bind Resource Pool dialog box, select the resource pool to be bound for Resource Pool.
    3. Click OK.
  4. View the connection status on the Enhanced tab page.
    • After an enhanced datasource connection is created, the status is Active, but it does not indicate that the queue is connected to the data source. Go to the queue management page to check whether the data source is connected. The procedure is as follows:
      1. In the navigation pane on the left, choose Resources > Queue Management. On the page displayed, locate a desired queue.
      2. Click More in the Operation column and select Test Address Connectivity.
      3. Enter the IP address and port number of the data source.
    • On the details page of an enhanced datasource connection, you can view information about the VPC peering connection.
      • VPC peering ID: ID of the VPC peering connection created in the cluster to which the queue belongs.

        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 CIDR block of the DLI queue, and do not delete the VPC peering connection during the datasource connection.

      • Status of the VPC peering connection:

        The status of a datasource connection can be Creating, Active, or Failed.

        If the connection status is Failed, click on the left to view the detailed error information.

        Figure 1 Viewing details