planetscale / planetscale/vitess-operator

problem on volume-subpaths (180G /var)

Open
#715 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
372
Forks
102
Avg merge
3d 5h
Merged PRs (30d)
15

Description

sudo du -h /var | grep G
...
4.6G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/vttablet/3/vt_0668433793/data/vt_coredb4
4.7G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/vttablet/3/vt_0668433793/data
4.1G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/vttablet/3/vt_0668433793/bin-logs
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/vttablet/3/vt_0668433793
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/vttablet/3
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/vttablet
4.6G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/mysqld-exporter/3/vt_0668433793/data/vt_coredb4
4.7G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/mysqld-exporter/3/vt_0668433793/data
4.1G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/mysqld-exporter/3/vt_0668433793/bin-logs
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/mysqld-exporter/3/vt_0668433793
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/mysqld-exporter/3
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/mysqld-exporter
4.6G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/mysqld/3/vt_0668433793/data/vt_coredb4
4.7G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/mysqld/3/vt_0668433793/data
4.1G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/mysqld/3/vt_0668433793/bin-logs
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/mysqld/3/vt_0668433793
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/mysqld/3
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26/mysqld
35G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths/pv-vitess-11-kpdbw26
36G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volume-subpaths
4.6G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volumes/kubernetes.iolocal-volume/pv-vitess-11-kpdbw26/vtdataroot/vt_0668433793/data/vt_coredb4
4.7G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volumes/kubernetes.io
local-volume/pv-vitess-11-kpdbw26/vtdataroot/vt_0668433793/data
4.1G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volumes/kubernetes.iolocal-volume/pv-vitess-11-kpdbw26/vtdataroot/vt_0668433793/bin-logs
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volumes/kubernetes.io
local-volume/pv-vitess-11-kpdbw26/vtdataroot/vt_0668433793
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volumes/kubernetes.iolocal-volume/pv-vitess-11-kpdbw26/vtdataroot
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volumes/kubernetes.io
local-volume/pv-vitess-11-kpdbw26
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volumes/kubernetes.io~local-volume
8.8G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8/volumes
44G /var/lib/kubelet/pods/bfd384cc-feac-4916-94ba-d6f5d52233b8
176G /var/lib/kubelet/pods
176G /var/lib/kubelet
180G /var/lib
180G /var

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the reported sudo du -h /var | grep G output and reproducing the disk-usage behavior around Kubernetes volume-subpaths. The issue names no repository files, tests, or requested change, so clarify the expected behavior and identify the relevant operator entry point before defining done.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.