grouper-dev - [grouper-dev] mysql database default transaction isolation level

Subject: Grouper Developers Forum

List archive

[grouper-dev] mysql database default transaction isolation level

From: "Hyzer, Chris" <>
To: "" <>
Subject: [grouper-dev] mysql database default transaction isolation level
Date: Sun, 8 May 2016 22:23:59 +0000
Accept-language: en-US
Authentication-results: internet2.edu; dkim=none (message not signed) header.d=none;internet2.edu; dmarc=none action=none header.from=isc.upenn.edu;
Spamdiagnosticmetadata: NSPM
Spamdiagnosticoutput: 1:23

Hey,

Oracle, postgres, hsqldb default to transaction isolation level: read committed

MySQL defaults to transaction isolation level: repeatable read

This causes problems in general, but also specifically in the grouper daemon (loader) which does work at the same time. Shilen has been working on this issue. We are interested in changing the default configuration for the database to be read committed for all databases. grouper.hibernate.base.properties:

hibernate.connection.isolation = 2

Obviously you could adjust this in the override properties file if you like (though you run the risk of constraint problems during concurrency).

Thoughts?

Thanks

Chris

[grouper-dev] mysql database default transaction isolation level, Hyzer, Chris, 05/08/2016

List archive

[grouper-dev] mysql database default transaction isolation level