Skip to Content.
Sympa Menu

grouper-users - [grouper-users] old records not removed from grouper_change_log_entry table

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] old records not removed from grouper_change_log_entry table


Chronological Thread 
  • From: Ben Beecher <>
  • To:
  • Subject: [grouper-users] old records not removed from grouper_change_log_entry table
  • Date: Tue, 29 Nov 2016 11:17:34 -0500
  • Ironport-phdr: 9a23:10eHgh98lYzBp/9uRHKM819IXTAuvvDOBiVQ1KB41eocTK2v8tzYMVDF4r011RmSDN6dsK0P0bOK+4nbGkU4qa6bt34DdJEeHzQksu4x2zIaPcieFEfgJ+TrZSFpVO5LVVti4m3peRMNQJW2aFLduGC94iAPERvjKwV1Ov71GonPhMiryuy+4ZPebgFGiTanb75/Lhq6oRvMusQZnIBvNrs/xhzVr3VSZu9Y33loJVWdnxb94se/4ptu+DlOtvwi6sBNT7z0c7w3QrJEAjsmNXs15NDwuhnYUQSP/HocXX4InRdOHgPI8Qv1Xpb1siv9q+p9xCyXNtD4QLwoRTiv6bpgRRn1gykFKjE56nnahMx+gqxYvRyvuQBwzpXOb42JLvdzZL/Rcc8YSGdHQ81fVzZBAoS5b4YXEucOI+BYpJTgqlQQsxSxGQmsC/31yjRVgXL5xrM13Po9HgHGwgMgBckDv2jTrNXxKacSVPu6zKjSwjnZcfxZxCr95ZHOfxs8ov+MRap9fdfPxUQsDQ/IjlGdpZbnMj+LzOgAvWyW4/J+We6zj2MrsQJ8rzi1yssylIXEiJgZxk3A+Ch6xos+OMe2R1RhYdG+FZtdryGaOJVyQsMlW2xovzs6yqEeuZ6heygF1ZEnyATea/yDb4SE/wjvW/qNLjtimH1lf7a/hwu38Ue7y+3zTNO430hXoSpYitXMt3YN2ALP6sWfV/dx4ESs1SyP2g3X8O1JI144mbDVJpMl2rIwk4AcsUXHHi/4gkX2i6qWe10k+uez9ejqba7rqYObN49wlwH+N78hms2lDugiLAcBQnWb9fym1LL/5U35XKlKjvoun6nWqpDaItkbpranDA9Py4oj9g2/ACm80NQDhnQHKFNFeAmbj4jyJV3COvH4DfGjg1uyijdrwe7JPqH/DpnXMHfMjarhLv5B7BtT0g0u1d1Foo9PB6saCPP1RkLrstHEVFk0PxHn7fzgDYBX24VWc2+CCa+UKuuGu1KF7eIiOcGHY4sIvTz8Ir4o6+O43ixxokMUYaT8hchfU3u/BPkze0g=

For the past two weeks we've been dealing with disk space issues in our Grouper database.  On 11/10 the data tablespace grew very large, apparently because we had assigned view privileges to a large number of users.  We have about 41700 reference groups and we had assigned the view privilege to each group for about 130000 users.  This produced a large number of transactions and the grouper_change_log_entry table grew very large.  On 11/17 there were 148 million records in that table and it was growing by 16 million records per day.  Our data tablespace grew from about 30GB to 171GB.  We truncated the grouper_change_log_entry table and we added these lines to the grouper-loader.properties file and restarted the loader:

loader.retain.db.logs.days=1
loader.retain.db.change_log_entry.days=1

We removed the view privileges for those 130000 users to the reference groups and that created several million new transactions.  We expected the table to shrink but it still has 131 million records.  It is currently growing by about 4133 records per day.  The old records are not being removed.  Our data tablespace has grown to 179GB.

Why are the old records not being removed from the grouper_change_log_entry table?
Should we truncate the table again?

The created_on field should contain milliseconds since epoch but those values are much larger than expected (E+15 instead of E+12):

sql> select (sysdate - to_date('01-Jan-1970', 'dd-Mon-yyyy')) * 86400000 from dual;

1.4804E+12   (millis since epoch for today)

sql> select created_on,TO_DATE('1970-01-01','YYYY-MM-DD') + created_on / 86400000 from grouper_change_log_entry where sequence_number=166996954;

CREATED_ON TO_DATE('
---------- ---------
1.4794E+15 25-OCT-14  (millis since epoch for the oldest record in that table)

sql> select created_on,TO_DATE('1970-01-01','YYYY-MM-DD') + created_on / 86400000 from grouper_change_log_entry where sequence_number=297672536;

CREATED_ON TO_DATE('
---------- ---------
1.4804E+15 23-AUG-46  (millis since epoch for the newest record in that table)

I set log level to DEBUG and I did not see any error messages in the log regarding the grouper_change_log_entry table.

Ben



Archive powered by MHonArc 2.6.19.

Top of Page