Subject: Grouper Users - Open Discussion List
- From: Tim Darby <>
- To: Shilen Patel <>
- Cc: Gagné Sébastien <>, "" <>
- Subject: Re: [grouper-users] PIT question
- Date: Tue, 30 Apr 2013 09:17:59 -0700
- Authentication-results: sfpop-ironport01.merit.edu; dkim=pass (signature verified [TEST])
The University of Arizona
Mosaic, Systems Integration and Architecture
UITS, Rm 335, 520-626-3799
Right, if the daemon is running properly, that temp table shouldn't have many entries unless you just did a large load and the change log processor is lagging behind.
By the way, if you run the PIT sync script and for some reason you're not having the daemon process the temp table, then the PIT sync script may not do what you expect. That process will fix issues but ignore cases where a temp change log entry hasn't been processed yet. So for example, if you create a group and that group is added to the temp change log but it's not added to point in time because the daemon isn't processing the temp change log, then running the PIT sync script will not add the group to point in time because that process is expecting the daemon to do the job since it sees that the group is still in the temp change log. Hopefully that makes sense. :)
You asked about starting over. You could clear out the temp change log and all the point in time tables and then run the PIT sync script.
Shouldn’t the grouper_change_log_entry_temp table normally be empty ? The Grouper Daemon should empty it and send it to grouper_change_log_entry.
De :  De la part de Tim Darby
Envoyé : 29 avril 2013 17:42
À : Shilen Patel
Objet : Re: [grouper-users] PIT question
I checked with our DBA team and it turns out that they already analyze the Grouper tables on a regular basis. They checked this query and determined that it needed indexes on string01 and string02 in grouper_change_log_entry_temp. This made a big difference.
On Mon, Apr 29, 2013 at 10:39 AM, Tim Darby <> wrote:
grouper_group_set - 4699169 rows
grouper_change_log_entry_temp - 1552245 rows
It's probably been at least a month since I analyzed tables, so I'll try that. Also, I don't really care if I lose the change log data. Is there a clean way to basically reset and start over?
On Mon, Apr 29, 2013 at 10:30 AM, Shilen Patel <> wrote:
After that message, the code is doing a database query and it seems that may be taking a while. How many rows do you have in grouper_group_set and grouper_change_log_entry_temp? Have you recently analyzed your tables?
When I run:
It pretty quickly runs through the various searches until it gets to:
Searching for missing active point in time group sets
and will not go past that point. It doesn't come back with "Found x missing..." and the GSH process in the UNIX process table is sleeping and stays that way for hours (I let it run overnight, just to see what would happen). Any ideas?
- [grouper-users] PIT question, Tim Darby, 04/29/2013
- Re: [grouper-users] PIT question, Shilen Patel, 04/29/2013
Archive powered by MHonArc 2.6.16.