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

Ignore EntryNotFound and AlreadyClosed errors when cleaning up cache #89

Merged
merged 1 commit into from
Nov 29, 2023

Conversation

mariash
Copy link
Member

@mariash mariash commented Nov 29, 2023

Please provide the following information:

What is this change about?

After container is deleted Rep cleans up the cache If cleaning up cache fails, we retry deleting container. If cleaning up cache fails because cache entry is not found Rep gets stuck in cleaning up containers and drain never exits. Cleaning up cache should be successful if cache entry is not found.

How should this change be described in diego-release release notes?

Cache cleanup after container deletion does not fail if cache entry is not found.

Please provide any contextual information.

Original issue in slack

Tag your pair, your PM, and/or team!

It's helpful to tag someone on your team or your team alias in case we need to follow up later.

Thank you!

If cache entry not found when cleaning up cache after container is
deleted we can ignore this error
@mariash mariash requested a review from a team as a code owner November 29, 2023 00:10
@ameowlia ameowlia merged commit 7d84fd3 into main Nov 29, 2023
1 check passed
@ameowlia ameowlia deleted the ignore-not-found branch November 29, 2023 17:02
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.

2 participants