GQLExecutor memory leak

[Dschoordsch]

The GQLExecutor memory consumption goes steadily up. As seen on here 🔒(top three lines)

the memory usage stayed high even through the weekend where I would expect it to drop.

[Dschoordsch]

Labelling it P3 as it's not critical now. Could be related to #8414

[Dschoordsch]

@rafaelromcar-parabol This could be an issue if we don't release for some time, like over christmas

[rafaelromcar-parabol]

We should keep an eye on it, for sure. But keep in mind that if the containers arrive to 4 GB of memory, they will be automatically restarted.

That said, we could restart the application next week before Christmas if needed. During the week or on the weekend. It can be done easily using the last pipeline in the Gitlab repository.

[rafaelromcar-parabol]

Also, I think this should be a P2. Mem leaks should always be fixed asap as they can affect stability. Even more in our application, that doesn't like restarting components very much. At least it didn't before this. Let's see after the release this week.

[mattkrick]

Blocked behind #9282

[rafaelromcar-parabol]

I was checking the memory usage on the GQL Ex and they are fine but at more than 60%. Which is fine, because if we do not release, the worst that can happen is having Kubernetes restarting them if they reach 100%. It isn't a big problem. Just sharing my thoughts here.

[mattkrick]

true for the saas! for certain clients who do do not manage their infra as diligently as we do, restarts may pose a problem 😅

[rafaelromcar-parabol]

Of course! I was talking about the Christmas period for the SaaS 😸 PPMIs haven't been updated in a long while. They are still in 6.83.0 and they have been like that for a while.

[jordanh]

Prioritized to backlog

[github-actions]

Stale issue