Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mitigate Potential Memory Pressure Effects With cgroup v2 #724

Closed
dariagrigoriu opened this issue Apr 18, 2023 · 1 comment
Closed

Mitigate Potential Memory Pressure Effects With cgroup v2 #724

dariagrigoriu opened this issue Apr 18, 2023 · 1 comment
Labels
ANNOUNCEMENT Announcement from the product group

Comments

@dariagrigoriu
Copy link
Collaborator

dariagrigoriu commented Apr 18, 2023 •
edited by torosent
Loading

Starting on 5/15/2023, Azure Container Apps will run on Azure Kubernetes version 1.25.* or higher.  In this version, Kubernetes uses cgroup v2 and can result in potential memory pressure effects for customers using JRE versions lower than 11.0.18, .NET < 6, nodejs, or any other framework that does not support cgroup v2, e.g. High memory consumption with v1.25.2 · Issue #3443 · Azure/AKS (github.com). Please consider framework version updates, memory usage optimizations, or allocating more memory to impacted apps.
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: triage 🔍 Pending a first pass to read, tag, and assign label Apr 18, 2023
@torosent torosent added ANNOUNCEMENT Announcement from the product group and removed Needs: triage 🔍 Pending a first pass to read, tag, and assign labels Apr 18, 2023
@torosent torosent pinned this issue Apr 18, 2023
@torosent torosent changed the title Potential Memory Pressure Effects Mitigate Potential Memory Pressure Effects With cgroup v2 Apr 18, 2023
@floriankoch
Copy link

NodeJs 20.3.0 has a fix for this (new libuv Version nodejs/node#48078)

@floriankoch floriankoch mentioned this issue Jul 17, 2023
Open
@simonjj simonjj unpinned this issue Jul 25, 2024
@cachai2 cachai2 closed this as completed Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ANNOUNCEMENT Announcement from the product group
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@dariagrigoriu @floriankoch @torosent @cachai2