Skip to content
MilvusNode SDK
Sections

Transfer replicas

Markdown

Copy for agent

Connection and CORS help

Use HTTPS for remote clusters or HTTP on loopback. Requests go directly from your browser to the endpoint. Run List collections to populate the collection selector. When copying an authenticated cURL command, set MILVUS_TOKEN in your shell.

For cross-origin requests, configure the endpoint to answer OPTIONS and allow the docs origin, POST, Content-Type, and Authorization if you use a token. Try the copied cURL command to troubleshoot outside the browser.

POST/v2/vectordb/resource_groups/transfer_replica

{
  "sourceRgName": "__default_resource_group",
  "targetRgName": "catalog_queries",
  "collectionName": "books",
  "replicaNum": 1
}

Example response

{
  "code": 0,
  "data": {}
}
cURL command
curl --request POST --url 'https://your-cluster.example.com/v2/vectordb/resource_groups/transfer_replica' \
  --header 'Content-Type: application/json' \
  --header "Authorization: Bearer ${MILVUS_TOKEN}" \
  --data-raw '{
  "sourceRgName": "__default_resource_group",
  "targetRgName": "catalog_queries",
  "collectionName": "books",
  "replicaNum": 1
}'

Move collection replicas between resource groups. The collection must be in the default database and the target group must have available query nodes.

Request fields

sourceRgName string (required)
Resource group that currently owns the replicas.
targetRgName string (required)
Resource group that should receive the replicas.
collectionName string (required)
Name of the collection.
replicaNum integer (required)
Number of collection replicas to transfer.

See HttpClient.transferReplica for the Node.js SDK method.