Memory leak or misconfiguration ? #1157
Unanswered
achedeuzot
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
On our most used endpoints where oathkeeper is used, we notice a progressive memory increase until the set limits where it gets killed by the OS because of the Out Of Memory issue.
Has anyone else experienced this with oathkeeper ? We're using the cache on
oauth2_introspection
and changing the cache to a lowmax_cost
doesn't help, neither does reducing the cache TTL.Happy to hear about your thoughts or experience about this 🙏
Beta Was this translation helpful? Give feedback.
All reactions