Best posts made by cyrill.lippuner

Hello,

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).

After cleaning that, everything is back to normal.

My proposition might be, to put a (maybe configurable) size limit on the *.data fields to prevent such hard to catch runtime errors.

Feel free to ask back for more info, I just wanted to put this here in case you might wanna consider it

Yeah, that was it... I guess it was already late

@dan Yes I did increase it until 2GB, but then loading a list of 4 users also fails ^^

So I think it is just not a good idea using FA as a database

Will look into the feature request.

Thanks, that was exactly what I was looking for. I just didn't stumble across this part of the docs.

To your question, I guess it is already at the right place. I would maybe just mention it in the create events and link this part of the docs as otherwise (at least in my case where most of the webhooks already work), I did not go back to the general webhook setup docs.

This is something I have already tried ad did not work. At least not with my setup. I have changed my setup and use now two databases instead of two schemas.