How you are dealing with growing evenstore size?
I'm currently working with self-hosted Zitadel at one of the projects.
As for now we are running v2 major release and have some issues with eventstore size - it'd reached 300 GiB and growing. Currently we start to cleanup some of old events we're not interested at (access and refresh token issue, for example) by smth like cron job, but this seems to be dirty hack and not the actual solution. More over, size of eventstore starts to affect Zitadel performance on long reads for soma APIs
AFAIK there is no docs or guides how to deal with eventstore size when it reaches out, so it'll be nice to have one as official solution after we discuss it here
At this tread I'd like to find meaningful solution for current problem and formalize it to become an official guide some where in FAQ, for example
As for now we are running v2 major release and have some issues with eventstore size - it'd reached 300 GiB and growing. Currently we start to cleanup some of old events we're not interested at (access and refresh token issue, for example) by smth like cron job, but this seems to be dirty hack and not the actual solution. More over, size of eventstore starts to affect Zitadel performance on long reads for soma APIs
AFAIK there is no docs or guides how to deal with eventstore size when it reaches out, so it'll be nice to have one as official solution after we discuss it here
At this tread I'd like to find meaningful solution for current problem and formalize it to become an official guide some where in FAQ, for example
