mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-01-03 11:45:20 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #6950 from Lyndon-Li/issue-fix-6663-design

Browse Source 
Design for node-agent concurrency
This commit is contained in:
Wenkai Yin(尹文开)
2023-11-08 09:04:05 +08:00
committed by GitHub
parent 6b7ce6655d a0edad94db
commit 866fbb5cdb
3 changed files with 128 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
design/volume-snapshot-data-movement/volume-snapshot-data-movement.md
View File

@@ -626,10 +626,9 @@ Therefore, we have below principles:
We will address the two principles step by step. As the first step, VBDM’s parallelism is designed as below:
- We don’t create the load balancing mechanism for the first step, we don’t detect the accessibility of the volume/volume snapshot explicitly. Instead, we create the backupPod/restorePod under the help of Kubernetes, Kubernetes schedules the backupPod/restorePod to the appropriate node, then the data movement controller on that node will handle the DataUpload/DataDownload CR there, so the resource will be consumed from that node.
- We don’t expose the configurable concurrency value in one node, instead, the concurrency value in value will be set to 1, that is, there is no concurrency in one node.
- We expose the configurable concurrency value per node, for details of how the concurrency number constraints various backups and restores which share VGDP, check the [node-agent concurrency design][3].
As for the resource consumption, it is related to the data scale of the data movement activity and it is charged to node-agent pods, so users should configure enough resource to node-agent pods.
Meanwhile, Pod Volume Backup/Restore are also running in node-agent pods, we don’t restrict the concurrency of these two types. For example, in one node, one Pod Volume Backup and one DataUpload could run at the same time, in this case, the resource will be shared by the two activities.
## Progress Report
When a DUCR/DDCR is in InProgress phase, users could check the progress.
@@ -970,4 +969,5 @@ Restore command is kept as is.
[1]: ../unified-repo-and-kopia-integration/unified-repo-and-kopia-integration.md
[2]: ../general-progress-monitoring.md
[2]: ../general-progress-monitoring.md
[3]: ../node-agent-concurrency.md