...

...

On This Page

Overview

When transferring data between a source and destination there are a number of factors which can limit the transfer speed.  Most cloud providers have rate limitations that reduce the transfer rate, but if those limits are account based and it supports impersonation, DryvIQ can create a pool of accounts that issues commands in a round-robin format across all of the accounts connected to the pool. Any modifications to the connection pool will used on the next job run. 

For example, if a connection pool has 2 accounts all commands will be alternated between them. If a third account is added to the pool, the next run of the job will use all three accounts.

Image Added

...

Connection Pools through the REST API

Creating a Connection Pool

1. Create the connections that should be in a connection pool. Keep track of connection IDs.

2. Using one of the connection IDs from previous step, create connection pool using REST API: 

PATCH {{url}}v1/connections/{{connection_id}}/pool

{
	"name":"New Connection Pool Name"
}

3. Note the pool:id in the response to the above command. This is the new connection Pool ID to be used when creating new jobs and to add more connections to the pool.

4. Add more connections (one by one) to the pool as needed.

PATCH {{url}}v1/connections/{{connection_id}}/pool

{
	"id":"{{connectionPool_id}}"
}

5. Create transfer job using {{connectionPool_id}} as the connection id.

Editing a Connection Pool

The Connection pool can be queried and additional connections can be added to a connection pool using the same REST API as above.

Deleting a Connection Pool

The Connection pool can be deleted using the REST API.

DELETE {{url}}v1/connections/{{connection__id}}/pool