-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
We have instructions telling people to run the bg job 'populate_stats_process_rooms', but it is a no-op #8238
Comments
It seems to me that one could add a new delta and (Fixing the existing delta file is not necessarily good as it has already gone out, and someone may be half-way through running the job when they upgrade to the version where we back out the |
@reivilibre I was planning to delete the progress again, but you're right in that I think we could keep the user's existing progress by just creating a new delta file. Thanks :) |
Oh, but we'll need to delete the progress anyways to cover the edge cases laid out in the original problematic delta file... |
You wouldn't need to delete the progress made by a i.e. a delta which:
should do as intended? |
@reivilibre After running through the possible upgrade paths through the notable versions ( |
Description
In this delta file we converted
populate_stats_process_rooms
to a no-op and createdpopulate_stats_process_rooms_2
in order to get around some edge cases with older Synapse versions.It seems that this was not necessary, and we could've kept the same name and simply purged the progress of and restarted background job in the delta file instead.
The chosen solution has problems as there are places that we tell people to use
populate_stats_process_rooms
to fix issues. These instructions now simply do nothing as the bg job is a no-op.A
DELETE
was used to solve a similar problem in another delta file:synapse/synapse/storage/databases/main/schema/delta/56/stats_separated.sql
Line 31 in a7bdf98
The delta file should be updated to sort out this mess.
The text was updated successfully, but these errors were encountered: