Skip to content

Geo: Increase requested memory for Geo Logcursor pod

Summary

From https://gitlab.com/gitlab-org/quality/gitlab-environment-toolkit-configs/staging-ref/-/issues/166#note_2184739566:

the issue here sounds like the Geo Logcursor, which is only deployed on the secondary, is causing resource contention in the Support pools

Requested memory for geo-logcursor pod is 700M. But in the secondary site of staging-ref.gitlab.com, memory usage regularly goes over 1G.

Geo Log Cursor pod memory usage

image

Steps to reproduce

Deploy an environment like staging-ref.

Configuration used

https://gitlab.com/gitlab-org/quality/gitlab-environment-toolkit-configs/staging-ref/

Current behavior

The actual and requested memory usage on the supporting node pool are not well aligned. The geo-logcursor pod seems to cause resource contention in the supporting node pool.

Expected behavior

The actual and requested memory usage on the supporting node pool are better aligned. The geo-logcursor pod does not seem to cause resource contention in the supporting node pool.

Versions

Relevant logs

See the staging-ref GCP project's logs.