Operator Excessive Logging W0409 09:44:32.943571 1 phase.go:74] volume tidb-rum/tikv-tidb-rum-tikv-3 modification is not allowed: can't shrink size from 3519Gi to 300Gi

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: [operator 大量刷日志 W0409 09:44:32.943571 1 phase.go:74] volume tidb-rum/tikv-tidb-rum-tikv-3 modification is not allowed: can’t shrunk size from 3519Gi to 300Gi](operator 大量刷日志 W0409 09:44:32.943571 1 phase.go:74] volume tidb-rum/tikv-tidb-rum-tikv-3 modification is not allowed: can't shrunk size from 3519Gi to 300Gi - TiDB 的问答社区)

| username: Hacker_qRmrPWkN

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version]: v6.5.8
[Reproduction Path] What operations were performed that caused the issue
[Encountered Issue: Issue Phenomenon and Impact] Currently migrating data centers, and there will be a large number of clusters deployed subsequently. Want to confirm if there are any issues.
[Resource Configuration]
[TiDB Operator Version]: 1.5.2
[K8s Version]: 1.21.14
[Attachments: Screenshots/Logs/Monitoring]
tidb operator tidb-controller-manager logs a lot:
W0409 09:44:32.943571 1 phase.go:74] volume tidb-rum/tikv-tidb-rum-tikv-3 modification is not allowed: can’t shrink size from 3519Gi to 300Gi
W0409 09:44:32.943579 1 phase.go:74] volume tidb-rum/tikv-tidb-rum-tikv-11 modification is not allowed: can’t shrink size from 3519Gi to 300Gi
W0409 09:44:32.943586 1 phase.go:74] volume tidb-rum/tikv-tidb-rum-tikv-12 modification is not allowed: can’t shrink size from 3519Gi to 300Gi
W0409 09:44:32.943593 1 phase.go:74] volume tidb-rum/tikv-tidb-rum-tikv-14 modification is not allowed: can’t shrink size from 3519Gi to 300Gi
W0409 09:44:32.943599 1 phase.go:74] volume tidb-rum/tikv-tidb-rum-tikv-19 modification is not allowed: can’t shrink size from 3519Gi to 300Gi
W0409 09:44:32.943605 1 phase.go:74] volume tidb-rum/tikv-tidb-rum-tikv-6 modification is not allowed: can’t shrink size from 3519Gi to 300Gi
W0409 09:44:32.943611 1 phase.go:74] volume tidb-rum/tikv-tidb-rum-tikv-1 modification is not allowed: can’t shrink size from 3519Gi to 300Gi
W0409 09:44:32.943618 1 phase.go:74] volume tidb-rum/tikv-tidb-rum-tikv-10 modification is not allowed: can’t shrink size from 3519Gi to 300Gi
W0409 09:44:32.943625 1 phase.go:74] volume tidb-rum/tikv-tidb-rum-tikv-16 modification is not allowed: can’t shrink size from 3519Gi to 300Gi
W0409 09:44:33.552146 1 phase.go:74] volume tidb-rum/pd-tidb-rum-pd-0 modification is not allowed: can’t shrink size from 3519Gi to 300Gi
W0409 09:44:33.552163 1 phase.go:74] volume tidb-rum/pd-tidb-rum-pd-1 modification is not allowed: can’t shrink size from 3519Gi to 300Gi
W0409 09:44:33.552169 1 phase.go:74] volume tidb-rum/pd-tidb-rum-pd-2 modification is not allowed: can’t shrink size from 3519Gi to 300Gi

2
| username: Jasper | Original post link

1. Regarding this error, some modifications were made to the operator-related logic in v1.5.2
v1.5.2 represents the actual size, while v1.4.0 represents the minimum size:
v1.5.2
Status.Capacity: Represents the actual resources of the underlying volume.

v1.4.0

Spec.Resources: Resources represent the minimum resources the volume should have.

2. The current error is caused by the mismatch between the 300g requested by the PVC and the actual size of the local PV, which is 3519g. There is no actual impact. If you are concerned about the log volume causing performance issues, you can adjust the PVC size to match the local PV size of 3519G to eliminate the error.

3
| username: dba远航 | Original post link

This is caused by the space shrinking too little.