You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Customizable limit for json blobs in *.data fields
Problem
This is not a direct bug, but maybe a safety net for other users to not do the same mistake as we did.
We had a prod environment going down due to fusionauth OOM errors which were cause by a bug on one of our services. There is everything fine with the FusionAuth in general, but the problem was that we filled up the users.data field for each user with too much data due to an error (should only have been a list of some bytes). Therefore, after some months we started to have some occasional OOM errors of FusionAuth, as the 0.5GB RAM were not sufficient anymore to load even a single user (which had a users.data text field of 400MB).
Solution
My proposition might be, to put a (maybe configurable) size limit on the json blob *.data fields to prevent such hard to catch runtime errors.
Alternatives/workarounds
I just cleared it manually in a routine and checked the size there.
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.
The text was updated successfully, but these errors were encountered:
Customizable limit for json blobs in
*.data
fieldsProblem
This is not a direct bug, but maybe a safety net for other users to not do the same mistake as we did.
We had a prod environment going down due to fusionauth OOM errors which were cause by a bug on one of our services. There is everything fine with the FusionAuth in general, but the problem was that we filled up the users.data field for each user with too much data due to an error (should only have been a list of some bytes). Therefore, after some months we started to have some occasional OOM errors of FusionAuth, as the 0.5GB RAM were not sufficient anymore to load even a single user (which had a users.data text field of 400MB).
Solution
My proposition might be, to put a (maybe configurable) size limit on the json blob
*.data
fields to prevent such hard to catch runtime errors.Alternatives/workarounds
I just cleared it manually in a routine and checked the size there.
Additional context
Got the suggestion to post it here in the forum.
https://fusionauth.io/community/forum/topic/2182/unlimited-data-fields?_=1664296262611
Community guidelines
All issues filed in this repository must abide by the FusionAuth community guidelines.
How to vote
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.
The text was updated successfully, but these errors were encountered: