ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15246) Set MySQL transaction isolation level to READ_COMMITTED
Date Thu, 03 Mar 2016 20:15:18 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-15246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178542#comment-15178542
] 

Hudson commented on AMBARI-15246:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #4437 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4437/])
AMBARI-15246. Set MySQL transaction isolation level to READ_COMMITTED. (mpapyrkovskyy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4fde93a2a1c908c82488f6ca555b37471dad2aac])
* ambari-server/src/main/java/org/apache/ambari/server/orm/EclipseLinkSessionCustomizer.java


> 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, 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)

Mime
View raw message