Support changing cacheVolume of cn and dn after mo is deployed #1170
Conversation
|
@aronchanisme need to review |
|
|
||
| ```bash | ||
| #获取 storageclass 信息 | ||
| >kubectl get storageclass ${SC_NAME} -oyaml #SC_NAME 是 mo 集群使用的 pvc 的 sc 类型 |
There was a problem hiding this comment.
可以提示一下，用这个命令可以查看STORAGE_CLASS的名称
[root@VM-0-122-tencentos ~]# kubectl get pvc -n ${MO_NS}
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
mo-data-mo-customer-test-cnset1-cn-rhv55 Bound pvc-5b8ed11a-bd16-4003-9d2e-0b17de76e4b9 100Gi RWO cbs-hssd 3h10m
mo-data-mo-customer-test-cnset1-cn-sddmf Bound pvc-804f64c4-c167-45b4-b82c-7af966a36971 100Gi RWO cbs-hssd 3h10m
mo-data-mo-customer-test-dn-0 Bound pvc-86d35491-b18c-4ad6-a685-95da970d211c 50Gi RWO cbs-hssd 3h10m
mo-data-mo-customer-test-log-0 Bound pvc-b6888a78-c946-498c-935e-cd1ae333c11a 100Gi RWO cbs-hssd 3h11m
mo-data-mo-customer-test-log-1 Bound pvc-fad96b55-b55e-4768-a80b-1d8e6168a2db 100Gi RWO cbs-hssd 3h11m
mo-data-mo-customer-test-log-2 Bound pvc-12416574-e763-4124-bebf-033e69bd2838 100Gi RWO cbs-hssd 3h11m
| ``` | ||
|
|
||
| 3. 按需修改 tn 和 cn 的 cacheVolume 的 size 大小。 | ||
|
|
There was a problem hiding this comment.
视乎修改的对象：
1、如果为CN group，则修改spec.cnGroups[0].cacheVolume（或spec.cnGroups[1].cacheVolume，其中[n]中的n为CN Group的数组下标）；
2、如果为CN，则修改spec.tp.cacheVolume
3、如果为TN，则修改spec.tn.cacheVolume（或spec.dn.cacheVolume）
|
|
||
| >kubectl get pvc -n ${MO_NS} | ||
|
|
||
| >kubectl get pv |
|
|
||
| 然后保存并退出：按 esq 键，和：wq | ||
|
|
||
| 4. 查看扩容结果 |
| size: 900Gi | ||
| ``` | ||
|
|
||
| 然后保存并退出：按 esq 键，和：wq |
|
@aronchanisme fixed，pls check again |
What type of PR is this?
Which issue(s) this PR fixes:
issue #1167
What this PR does / why we need it: