I’ve recently noticed that we’ve got some
check processes that are spawned on our Concourse workers from some
check containers that are consuming nearly 2 GB of memory as measured by
top. It can happen that multiple
check processes can appear at the same time and that each consume ~2 GB of memory, resulting in several GB of memory eaten up for resource checks. Some of our users’ jobs are now being terminated by the OOM killer, and I suspect that these check processes are to blame.
The problem is that I cannot find a way to identify which resources the check containers belong to so that I can debug this.
I know that there are some tickets concerning this issue (see below) that were closed because check containers will no longer exist in the near future. Regardless, can someone provide a work-around that will allow me to determine the pipeline and resource of a check container given its ID? Thanks a bunch!