Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] findBadMemberships job failure after taking latest patches

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] findBadMemberships job failure after taking latest patches


Chronological Thread 
    < Chronological >      < Thread >
  • From: Shilen Patel <>
  • To: "Rahman, Mahbub" <>
  • Cc: "" <>
  • Subject: Re: [grouper-users] findBadMemberships job failure after taking latest patches
  • Date: Tue, 7 Jan 2020 12:20:02 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=duke.edu; dmarc=pass action=none header.from=duke.edu; dkim=pass header.d=duke.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=411R1PHkUbFeQiFXzCcTsj8v7jLBGtxfEyjdIOIU1s8=; b=Wpo2F2tCk/iFho0Lz6ZIRSYciY/4WeWVhAxvXbzaJOTLKjnkbLhBEG8GPFntESlKK2hQkg6nhVTEdMb2RnOhZv6ViejStgr1xR5QFgiOnm0ppY6P73VFILbQgwOFaxuq1tdFZRr2MjKsa7eXCcWV1Cy50LdnQOuM81L6qIybunQ/BxWiCOvQTHFYq55olRQxzLYRfq0YxkKzre3B/lMIYVh1uaCsRyZe6FSlYMJdyu2LQMon/oJh9qwrRCxD+oiwX4Iggo73DvA55++T/S9Kgc6+XSf+KtKoIPBSv+ieVW89/oZq/+4jHWo1O+YT38+jKStH3zA6QuFjErHxm7StKg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ikDAY/W4NUiVpKgKs4QMQnRsEPM94QD+W8DVGXOGGMdz+b0N4zFAV0DcICjULDVqKq3Ya96lMX9GuVkHpIPq+DfUHVTsziVP8aPjrT30yNpkdNhS5IJqT3Z1lj/RyVRLLcylH5LIzrTINYg9Jjikaf0MCpxQg/CJ5BbDqXCv9/Hmf4CwCMUik94o6IM6n7tFCNr8G1LdLEOoMeFn8gDW7tQusd2c+8zITVumF0BoAFH008UM3JkVrn5DuJvMzMwjnrCcIOs5u8+g0MEm9MEVQ3JmABpTY6uErOTrKT1DKDtb5F4e5dHotqvvgn4G+r4xSVOlbhX5B9nRi2VesDXEgQ==

Hi Mahbub,

 

Do you have a stack trace?  If you run the problematic query manually, does it run but take a long time? 

 

Thanks!

 

- Shilen

 

From: <> on behalf of "Rahman, Mahbub" <>
Reply-To: "Rahman, Mahbub" <>
Date: Monday, January 6, 2020 at 3:30 PM
To: "" <>
Subject: [grouper-users] findBadMemberships job failure after taking latest patches

 

Hello,

 

We are using clustered AWS aurora mysql RDS (engine version: mysql 5.7.mysql_aurora.2.04).

After taking the latest v2.4.0 patches, findBadMemberships job is failing for me with connection timed out error. It looks like the query changes applied as part of GRP-2080 and GRP-2117 is causing this error in our environment (from EXISTS to IN clause for sub queries).

I have the indices applied for grouper_composites.type grouper_attribute_assign.attribute_assign_type and the tables are analyzed.

We would appreciate your insight and recommendations to resolve this issue.

 

Thanks,

Mahbub


Archive powered by MHonArc 2.6.19.

Top of Page