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.

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

add grpcio 1.57.0 pin to provided helm chart images #26630

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

gibsondan
Copy link
Member

Summary:
Attempt to resolve reported memory leak versions with . Apparently the underlying issue is also resolved in python 3.13, so once we officially support that in dagster, we could potentially move these images to 3.13 and remove this.

Test Plan:
Deploy the helm chart locally with these built images

Changelog:
Added a pin to the grpcio version used by the Dagster Helm chart daemon and webserver images, to a version that has been reported to avoid memory leaks.

Summary & Motivation

How I Tested These Changes

Changelog

Insert changelog entry or delete this section.

Summary:
Attempt to resolve reported memory leak versions with . Apparently the underlying issue is also resolved in python 3.13, so once we officially support that in dagster, we could potentially move these images to 3.13 and remove this.

Test Plan:
Deploy the helm chart locally with these built images

Changelog:
Added a pin to the grpcio version  used by the Dagster Helm chart daemon and webserver images, to a version that has been reported to avoid memory leaks.
Copy link
Contributor

@danielgafni danielgafni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe include the github issue in the comment for documentation purposes?

#18997

@@ -13,4 +13,5 @@ RUN python -m uv pip install \
-e dagster-k8s \
-e dagster-celery[flower,redis,kubernetes] \
-e dagster-celery-k8s \
-e dagster-webserver
-e dagster-webserver \
grpcio==1.57.0 # workaround for reported memmory leak issues with later versions of grpc
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

something in the comment / link to make it easier for future person to know if its safe to remove

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants