`grootfs clean` process is triggered by the garden on the Diego cell to clean up unused image files; only one process should be running at a single time. However, it is observed that growing `grootfs. clean` processes and extremely high CPU & memory resources are consumed by those processes.
... 1 ####02 ####094 ####31 ? -1 Sl 0 0:00 /var/vcap/packages/grootfs/bin/grootfs --log-file /var/vcap/sys/log/garden/groot.clean.log --log-level info --log-timestamp-format rfc3339 --store /var/vcap/data/grootfs/store/unprivileged --metron-endpoint 127.0.0.1:3457 --tardis-bin /var/vcap/packages/grootfs/bin/tardis --newuidmap-bin /var/vcap/packages/garden-idmapper/bin/newuidmap --newgidmap-bin /var/vcap/packages/garden-idmapper/bin/newgidmap clean --threshold-bytes 0 ...
TPCF 6.x
The root cause is not identified, but the direct cause is how `grootfs` handles lock.
This issue is fixed in TPCF v6.0.21+ or v10.2.4+.
In case a temporary workaround is pursued, here are the procedures below:
In case the above procedures do not work, try the following two commands:
1. First, filter out processes with this command.
ps -ef | grep "/var/vcap/packages/garden-idmapper/bin/newgidmap clean" | grep -v grep | awk '{print $2}'
2. Then kill those processes once confirmed.
ps -ef | grep "/var/vcap/packages/garden-idmapper/bin/newgidmap clean" | grep -v grep | awk '{print $2}' | xargs kill