Subject: Grouper Users - Open Discussion List
[grouper-users] PIT table functionality and Grouper database size control
- From: Rory Larson <>
- To: "" <>
- Subject: [grouper-users] PIT table functionality and Grouper database size control
- Date: Tue, 13 Nov 2018 04:21:37 +0000
- Accept-language: en-US
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
I'd like to revisit an issue we were discussing at the end of January and the beginning of February. We have a Grouper database on a physical server that cannot expand its disk space, and the database is growing to around 80% - 90% of the disk and theatening to choke itself. The database is MariaDB, which does not free up space when records are deleted in the usual way. Last February, we were able to get 38 GB back by truncating the grouper_audit_entry table, and that solved the immediate crisis. Now we are back to the same situation again, driven in part by two large PIT tables, grouper_pit_group_set and grouper_pit_memberships.
If I were to truncate these tables, i.e. delete all data in them while leaving the tables intact, would it do any damage to Grouper as a functioning system? Yes, I would lose the history.
Alternatively, we might try deleting just the inactive records from these tables. I believe these would be all the ones where active = 'F'. Or, Shilen kindly shared a gsh command last January 29:
gsh% edu.internet2.middleware.grouper.pit.PITUtils.deleteInactiveRecords(new Date(), true);
On a test server, this seemed to be deleting other than just the PIT tables, and at present is dying with a Java error before it gets to them. In either case, we would presumably have to do a mysqldump, table delete, and restore from the dump file to get the space. Would this be safe to do with only the Grouper loader off, or would we need to take down Grouper altogether?
- [grouper-users] PIT table functionality and Grouper database size control, Rory Larson, 11/13/2018
Archive powered by MHonArc 2.6.19.