Skip to content

Commit 465ddea

Browse files
committed
update documentation and makefile for the changes in the bash script
1 parent 85e07cd commit 465ddea

2 files changed

Lines changed: 9 additions & 7 deletions

File tree

Makefile

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -180,9 +180,9 @@ backup-sonarqube:
180180

181181

182182
# PVC MIGRATION
183-
## Migrate data from one PVC to another.
183+
## Migrate data from one PVC to another. Options: SOURCE_PVC, TARGET_PVC, THREADS (default: 5), CPU_REQUEST (default: 1)
184184
migrate-pvc-data:
185-
./scripts/migrate_pvc_data.sh --source-pvc $(SOURCE_PVC) --target-pvc $(TARGET_PVC) --namespace $(ODS_NAMESPACE)
185+
./scripts/migrate_pvc_data.sh --source-pvc $(SOURCE_PVC) --target-pvc $(TARGET_PVC) --namespace $(ODS_NAMESPACE) --threads $(THREADS) --cpu $(CPU_REQUEST)
186186
.PHONY: migrate-pvc-data
187187

188188

docs/modules/administration/pages/pvc-migration.adoc

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,15 @@ To migrate data between PVCs, follow these steps:
1616

1717
[source,sh]
1818
----
19-
make migrate-pvc-data SOURCE_PVC=<source-pvc-name> TARGET_PVC=<target-pvc-name>
19+
make migrate-pvc-data SOURCE_PVC=<source-pvc-name> TARGET_PVC=<target-pvc-name> [THREADS=<num-threads>] [CPU_REQUEST=<num-cpu>]
2020
----
2121

22-
Replace `<source-pvc-name>`, and `<target-pvc-name>` with the appropriate values for your environment.
22+
Replace `<source-pvc-name>`, `<target-pvc-name>`, `<num-threads>`, and `<num-cpu>` with the appropriate values for your environment.
23+
- `THREADS` (optional): Number of parallel threads to use for migration (default: 5).
24+
- `CPU_REQUEST` (optional): Number of CPU cores to request for the migration pod (default: 1).
2325

2426
== Details
2527

26-
- The migration process creates a temporary pod that uses `rsync` to copy data from the source PVC to the target PVC.
27-
- Logs of the migration are stored in `/tmp/target/rsync.log` within the target PVC.
28-
- After the migration, verify the data integrity and delete the temporary pod if necessary.
28+
- The migration process creates a temporary pod that uses parallelized `rsync` to copy data from the source PVC to the target PVC.
29+
- You can control the number of parallel threads and CPU resources via the `THREADS` and `CPU_REQUEST` options.
30+
- After the migration, verify the data integrity and delete the temporary pod.

0 commit comments

Comments
 (0)