[
https://issues.apache.org/jira/browse/AMBARI-12503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14637430#comment-14637430
]
Hudson commented on AMBARI-12503:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3152 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3152/])
AMBARI-12503. Display a warning if Oozie is configured with Derby as the db
store (alexantonenko) (hiveww:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=497eed3b214b23501d7ffe825096b1e56accd8e8)
* ambari-web/app/controllers/wizard/step7_controller.js
* ambari-web/app/messages.js
* ambari-web/test/controllers/wizard/step7_test.js
> Display a warning if Oozie is configured with Derby as the db store
> -------------------------------------------------------------------
>
> Key: AMBARI-12503
> URL: https://issues.apache.org/jira/browse/AMBARI-12503
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.1.1
>
> Attachments: AMBARI-12503.patch
>
>
> As discussed, it would be good to display a warning if Derby is used as the
> database for Oozie. While it is useful for quick development or sandbox
> envs, for production we should advise users to use a supported DB like MySQL,
> Postgres or Oracle
> Embedded derby does not allow concurrent connections and is not supported for
> Oozie HA and will cause slow running of Oozie in action progress under
> heavier workloads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
