You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Myroslav Papirkovskyy (JIRA)" <ji...@apache.org> on 2016/03/01 16:54:18 UTC
[jira] [Updated] (AMBARI-15246) Set MySQL transaction isolation
level to READ_COMMITTED
[ https://issues.apache.org/jira/browse/AMBARI-15246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myroslav Papirkovskyy updated AMBARI-15246:
-------------------------------------------
Attachment: AMBARI-15246.patch
Unit tests are not applicable. DB-specific config changed.
> Set MySQL transaction isolation level to READ_COMMITTED
> -------------------------------------------------------
>
> Key: AMBARI-15246
> URL: https://issues.apache.org/jira/browse/AMBARI-15246
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Myroslav Papirkovskyy
> Assignee: Myroslav Papirkovskyy
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15246.patch
>
>
> MySQL sets default transaction isolation level to REPEATABLE_READ.
> This doesn't match other databases (Oracle, Postgres) and default EclipseLink shared cache behavior.
> We should change it to have same behavior for all database options.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)