Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Add composite as member takes really long time - MariaDB

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Add composite as member takes really long time - MariaDB

Chronological Thread 
  • From: Shilen Patel <>
  • To: Carl Waldbieser <>
  • Cc: grouper-users <>
  • Subject: Re: [grouper-users] Add composite as member takes really long time - MariaDB
  • Date: Mon, 30 Apr 2018 19:12:33 +0000
  • Accept-language: en-US
  • Authentication-results:; spf=none
  • Ironport-phdr: 9a23:VVMrEhLeBkkj8UUNF9mcpTZWNBhigK39O0sv0rFitYgeKfzxwZ3uMQTl6Ol3ixeRBMOHs6kC07KempujcFRI2YyGvnEGfc4EfD4+ouJSoTYdBtWYA1bwNv/gYn9yNs1DUFh44yPzahANS47xaFLIv3K98yMZFAnhOgppPOT1HZPZg9iq2+yo9JDffwtFiCChbb9uMR67sRjfus4KjIV4N60/0AHJonxGe+RXwWNnO1eelAvi68mz4ZBu7T1et+ou+MBcX6r6eb84TaFDAzQ9L281/szrugLdQgaJ+3ART38ZkhtMAwjC8RH6QpL8uTb0u+ZhxCWXO9D9QKsqUjq+8ahkVB7oiD8GNzEn9mHXltdwh79frB64uhBz35LYbISTOfFjfK3SYMkaSHJBUMhPSiJBHo2yYYgBAOoAIelWoIbyqkASrRSlAAmgGP/jxyVKi3LwwKY00/4hEQbD3AE4AtwOsHXUrNHrO6cUTOu71rPHzSndYPNSxDzw75PIchAgofGIQ71wd9HcxlQyFwPGkFqcs5LqMC6I1ukUtWWQ8uluVfq3hmI6qwx9vCKjy8k2hoXUhY8YzkrI+Tt2zYs1PdG0VU52bcC+HJZerS2XOYR7TtksTm1wtiY11L4LtYK+cSUP1Jso2QDTZvmDfoWL7BLsT+OcLDN3iX54fL+yghW//Eakx+LmUMS/zUxEoTBfktbWs3AAzxzT5daDSvt65kqh3CyA1wHX6u1dLkA1m7PXJ4Mlz7IqkZoTsFjDEjXrl0Xrj6+ZaF8o9fa15OT6ernmp5mcOJFoigzmL6gjmtKzDf42PwQUQmSW+uCx2Kf98UD2QLhGlvg2nbPYsJDeK8QbvKm5AwpN34Y46xa/DjOm38oenXQcMV1FZRGHgJbzN17QPf/4EO+zg06wnzdz2/DGIrrhD43CLnjZl7fhYK595FBGyAYq0NBf/IxbCqsaIP/oXk/xtcfYDgMiMwCq2ernCdN91p8AVmKVBK+WLr/SvUGS6u0xPuaMedxdhDGoAPE/47bRhHs1k14QZqSzlc8IYXS0FPVrKG2daHTlk9odDWpMswYjGr/EklqHBAVTZnK/WeoE7y02DMryFofCQo2rqLCc3yr9E5FLMDMVQmuQGGvlIt3XE8wHbzifd4o4ymQJ
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

Hi Carl,

Are you able to reproduce this issue using GSH and while it’s hanging, do a
‘kill -3’ or jstack and send the stacktrace so we can see where the problem


- Shilen

On 4/30/18, 11:42 AM,
on behalf of Carl Waldbieser"
on behalf of

I experienced a strange error in Grouper this morning.
I have my standard "allow" and "deny" groups for a policy. I wanted to
add a cohort to the allow policy, but there were some particular exclusions I
needed to apply to the cohort list I was provided.
I created a reference group for the provided cohort, and a reference
group for the exclusions, and then I created a composite group that was the
provided cohort minus the exclusions. So far so good. The composite ended
up having 247 members.

Next, I attempted to add this composite to my "allow" policy. This ended
up timing out in the UI. I tried adding the composite to the "allow" policy
using GSH, and after a short period of time, I received a stack trace. In
the Grouper logs, I saw:

ERROR JDBCExceptionReporter.logExceptions(234) - - Lock wait timeout
exceeded; try restarting transaction

I contacted our DB admins. The DB admin found a lock originating from a
sleeping Grouper process and killed it. I tried to re-run from GSH again
while the DB admin monitored the progress. This time the query ran for 10
minutes. The DB admin could see it had created a temp table while holding
~50,000 row locks.

At this point I terminated the client connection and the transaction
rolled back on the DB side. I exported the composite group membership to a
spreadsheet, then imported the membership into a "workaround" reference
group. I was able to add this workaround group to the "allow" policy without
any issues, and it took only a second or two for the operation to complete
using the UI.

I tried searching the Jira for this issue, but I didn't turn up any
results. Has anyone run into an issue similar to this? We are running
Grouper 2.2.1 with a MariaDB cluster back end.

Is there any reason why adding a composite caused the issue vs. adding a
static cohort?

Carl Waldbieser
ITS Identity Management
Lafayette College

Archive powered by MHonArc 2.6.19.

Top of Page