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

Should it be possible to configure shorter namespace lifetimes than the cleanup loop checks? #236

Open
Payback159 opened this issue Aug 30, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@Payback159
Copy link
Owner

Payback159 commented Aug 30, 2023

Describe the bug

If the namespace lifetime is smaller than cleanupInterval in the tenama configuration, the namespace may still exist longer than desired.

To Reproduce
Steps to reproduce the behavior:

  1. set cleanupInterval in the tenama configuration for example to 15m
  2. create namespace with a lifetime of 5m
  3. wait for 5m if the loop isn't random synced with the namespace lifetime the namespace will exist after 5m

Expected behavior
I would expect that the namespace will be cleared after it's configured lifetime.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context

I think at the moment the problem exists because the cleanup logic is based on a timely based loop which is execute in a configureable time (in the example all 15m). Maybe we can implemented an api-watcher which get's notified when the lifetime of a namespace is reached and cleans it on a more event-based way.

Alternative we can implement that the namespace lifetime can't be smaller than the cleanupInterval but I think that would be not the best solution.

@Payback159 Payback159 added the bug Something isn't working label Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant