Comment on Cleaning up the database
harald@hub.volse.no@hub.volse.no 21 hours ago
@Hans van Zijst There's a few things I can think of: Check your xconfig table. I've had issues with it growing a lot for different reasons in the past. Sometimes the real size of the data may be way smaller than the space they occupy on disk, due to frequent updates leading to fragmentation.
You can find some useful queries in framagit issue #1927.
In that case it seemed some indexes had disappeared from the database, which is also worth checking. That caused a lot of duplicate entries in the db.
Another issue I've seen more recently was that the queueworker built up a huge number of jobs. This seems to be due to trying to fetch parents and all downstream comments from messages arriving at the hub somehow. Check the queueworkers page in admin, and the workerq table in the db.
Again, this table is updated frequently, so may be subject to fragmentation.
See framagit issue #1972 for some more background on this.
Other than that. Just see which table are taking up the space in your DB. It should be the
Good luck!
You can find some useful queries in framagit issue #1927.
In that case it seemed some indexes had disappeared from the database, which is also worth checking. That caused a lot of duplicate entries in the db.
Another issue I've seen more recently was that the queueworker built up a huge number of jobs. This seems to be due to trying to fetch parents and all downstream comments from messages arriving at the hub somehow. Check the queueworkers page in admin, and the workerq table in the db.
Again, this table is updated frequently, so may be subject to fragmentation.
See framagit issue #1972 for some more background on this.
Other than that. Just see which table are taking up the space in your DB. It should be the
items table, and pretty much everything else should be small in comparison. If that's not the case, some investigation is needed.Good luck!