-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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.
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
Retention policy not working without any new activity #12093
Comments
I can reproduce the same behaviour on 0.69.2 with 2 running instances |
+1 same here on 0.69.2 |
This behaviour is originally on purpose, as added by @ggazzo, and also discussed in #11725, as it adds a performance boost. However, it's worth the effort to consider making this optional or removing this behavior altogether in favor of faster deletion. I've been very busy lately, so I don't have much time to pick this up. But if I do have the time, I'll try to pick it up, together with some other related issues. |
Actually, for our case, we do not care for processing power. So the ideal is to add a boolean option that allows the user to select whether he/she wants to force pruning or keep the standard behavior:
As a workaround, we are using a crontabbed script that calls the API and posts a dummy message every 24 hours, on every single channel. Which is so ugly :( Thanks for your reactiveness. @ggazzo Please change the milestone to 0.72.0 as 0.71.0 is already packaged without the fix. |
sorry guys I was/am working with another issues, this week I will fix :) |
+1 |
Any progress on this bug? |
closed by #15252 |
Description:
We are currently testing the retention policy and we have the behavior that channels, rooms and private messages are not deleted if there is no new message/activity. When someone writes a new message, messages older than one day were deleted after 30 minutes. But without a new message, we can see messages older than 1 day.
Settings:
Steps to reproduce:
Expected behavior:
I expect that alle messages will be deleteted after 1 day even if no new message was written
Actual behavior:
Server Setup Information:
The text was updated successfully, but these errors were encountered: