You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Aleksandr Kovalenko (JIRA)" <ji...@apache.org> on 2015/07/22 17:58:04 UTC
[jira] [Commented] (AMBARI-12503) Display a warning if Oozie is
configured with Derby as the db store
[ https://issues.apache.org/jira/browse/AMBARI-12503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14637112#comment-14637112 ]
Aleksandr Kovalenko commented on AMBARI-12503:
----------------------------------------------
+1 for the patch
> 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)