# Manage Query Nodes and Resource Groups

Allocate Milvus query nodes and collection replicas with resource groups, and use the Node.js SDK to inspect or move them.

SDK: `@zilliz/milvus2-sdk-node@3.0.10` · Tested with Milvus 3.0.6

Canonical documentation: https://milvus-io.github.io/milvus-sdk-node/management/resource-management/

## Section links

- [Resource Groups](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#resource-groups)
- [Create Resource Group](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#create-resource-group)
- [List Resource Groups](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#list-resource-groups)
- [Describe Resource Group](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#describe-resource-group)
- [Update Resource Group](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#update-resource-group)
- [Drop Resource Groups](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#drop-resource-groups)
- [Node Management](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#node-management)
- [Transfer Node](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#transfer-node)
- [Replica Management](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#replica-management)
- [Transfer Replica](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#transfer-replica)
- [Resource Group Configuration](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#resource-group-configuration)
- [Configuration Structure](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#configuration-structure)
- [Transfer Policies and Node Filters](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#transfer-policies-and-node-filters)
- [Best Practices](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#best-practices)
- [Next Steps](https://milvus-io.github.io/milvus-sdk-node/management/resource-management/#next-steps)

This guide covers resource group management and node/replica operations.

## Resource Groups

Resource groups allow you to organize and manage compute resources.

### Create Resource Group

Create a new resource group:

```javascript
await client.createResourceGroup({
  resource_group: 'rg1',
  config: {
    requests: {
      node_num: 2,
    },
    limits: {
      node_num: 4,
    },
  },
});
```

### List Resource Groups

List all resource groups:

```javascript
const groups = await client.listResourceGroups();

console.log('Resource groups:', groups.resource_groups);
```

### Describe Resource Group

Get detailed information about a resource group:

```javascript
const info = await client.describeResourceGroup({
  resource_group: 'rg1',
});

console.log('Resource group info:', info);
```

### Update Resource Group

Update resource group configuration:

```javascript
await client.updateResourceGroups({
  resource_groups: {
    rg1: {
      requests: { node_num: 3 },
      limits: { node_num: 6 },
    },
  },
});
```

### Drop Resource Groups

Delete resource groups:

```javascript
await client.dropResourceGroup({ resource_group: 'rg1' });
```

## Node Management

### Transfer Node

Move a node to a different resource group:

```javascript
await client.transferNode({
  source_resource_group: 'rg1',
  target_resource_group: 'rg2',
  num_node: 1,
});
```

## Replica Management

### Transfer Replica

Move replicas to a different resource group:

```javascript
await client.transferReplica({
  source_resource_group: 'rg1',
  target_resource_group: 'rg2',
  collection_name: 'my_collection',
  num_replica: 1,
});
```

## Resource Group Configuration

### Configuration Structure

```javascript
{
  requests: {
    node_num: 2,        // Requested number of nodes
  },
  limits: {
    node_num: 4,        // Maximum number of nodes
  },
}
```

### Transfer Policies and Node Filters

Resource group configuration can also define where to borrow missing nodes from, where to send redundant nodes, and which node labels are allowed in the group.

```javascript
await client.updateResourceGroups({
  resource_groups: {
    rg1: {
      requests: { node_num: 2 },
      limits: { node_num: 4 },
      transfer_from: [{ resource_group: '__default_resource_group' }],
      transfer_to: [{ resource_group: 'rg_overflow' }],
      node_filter: {
        node_labels: [{ key: 'workload', value: 'search' }],
      },
    },
  },
});
```

When describing a resource group, the response includes node and movement details when Milvus returns them:

```javascript
const info = await client.describeResourceGroup({
  resource_group: 'rg1',
});

console.log('Available nodes:', info.resource_group.num_available_node);
console.log('Incoming nodes:', info.resource_group.num_incoming_node);
console.log('Outgoing nodes:', info.resource_group.num_outgoing_node);
console.log('Nodes:', info.resource_group.nodes);
```

## Best Practices

1. **Organize by workload**: Create resource groups for different workloads
2. **Set appropriate limits**: Configure limits based on available resources
3. **Monitor usage**: Regularly check resource group usage
4. **Balance resources**: Use transfer operations to balance load

## Next Steps

- Learn about [Collection Management](https://milvus-io.github.io/milvus-sdk-node/management/collection-management/)
- Explore [Best Practices](https://milvus-io.github.io/milvus-sdk-node/advanced/best-practices/)
