Skip to content

fix(clustering): lmdb cache should prioritize over declaritive config #14411

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
Closed
wants to merge 1 commit into from
Closed

fix(clustering): lmdb cache should prioritize over declaritive config #14411

wants to merge 1 commit into from

Conversation

@StarlightIbuki
Copy link
Contributor

@github-actions github-actions bot added the cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee label Apr 10, 2025
@StarlightIbuki StarlightIbuki force-pushed the fix/cache-priority-lmdb-over-declartive branch from f98dbd7 to 0603480 Compare April 10, 2025 08:51
@StarlightIbuki StarlightIbuki marked this pull request as draft April 10, 2025 09:31
@StarlightIbuki StarlightIbuki force-pushed the fix/cache-priority-lmdb-over-declartive branch from 0603480 to ff317e0 Compare May 14, 2025 03:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@chronolaw chronolaw Awaiting requested review from chronolaw

@dndx dndx Awaiting requested review from dndx

@aboudreault aboudreault Awaiting requested review from aboudreault

Assignees

@StarlightIbuki StarlightIbuki

Labels

cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee size/M skip-changelog

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

There seems to be a problem with the loading priority of declarative_config and LMDB cache file in hybrid mode

2 participants

@StarlightIbuki