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
{{ message }}
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
device_list_stream is stored inefficiently, leading to massive disk space use #1962
the device_list_stream table is supposed to store deltas of device lists (ie, just the devices which change), but sometimes it gets confused and ends up storing the entire device list for certain users.
We have users who have over 6000 devices (which is a separate problem), so it's possible to churn through disk space at gigabytes per hour.
we also SELECT user_id FROM device_lists_stream WHERE stream_id > ?, rather than SELECT DISTINCT, so the query result is potentially huge, which can make synapse use all the memory.
Activity
richvdh commentedon Mar 2, 2017
we also
SELECT user_id FROM device_lists_stream WHERE stream_id > ?, rather thanSELECT DISTINCT, so the query result is potentially huge, which can make synapse use all the memory.richvdh commentedon Mar 3, 2017
To check if you are being affected by this, connect to the database and:
if the above shows users with many entries, you can delete them with:
(Note that this may harm your ability to communicate with that user using end-to-end-encryption).
richvdh commentedon Mar 8, 2017
fixed in #1964 / #1969, I think.