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

fix(kuma-cp): cleanup interval should be calculated based on "expirationTime" for hashCache #8065

Merged

Conversation

lobkovilya
Copy link
Contributor

hashCache has an expiration time of 1m, but the cleanup interval was 900ms

Checklist prior to review

  • Link to relevant issue as well as docs and UI issues --
  • This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
  • Tests (Unit test, E2E tests, manual test on universal and k8s) --
    • Don't forget ci/ labels to run additional/fewer tests
  • Do you need to update UPGRADE.md? --
  • Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label) --

…ionTime" for hashCache

Signed-off-by: Ilya Lobkov <ilya.lobkov@konghq.com>
@lobkovilya lobkovilya requested a review from a team as a code owner October 18, 2023 09:57
@lobkovilya lobkovilya requested review from michaelbeaumont and slonka and removed request for a team October 18, 2023 09:57
@lobkovilya lobkovilya merged commit 68fdb09 into kumahq:master Oct 18, 2023
7 checks passed
@lobkovilya lobkovilya deleted the fix/increase-cache-janitor-interval branch October 18, 2023 10:32
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