Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 22 Jul 2015 15:57:05 +0000 (UTC)
From: "Antonenko Alexander (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12846930.1437579406000.257541.1437580625123@Atlassian.JIRA>
In-Reply-To: <JIRA.12846930.1437579406000@Atlassian.JIRA>
References: <JIRA.12846930.1437579406000@Atlassian.JIRA>
 <JIRA.12846930.1437579406022@arcas>
Subject: [jira] [Updated] (AMBARI-12503) Display a warning if Oozie is
 configured with Derby as the db store
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-12503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonenko Alexander updated AMBARI-12503:
-----------------------------------------
    Attachment: AMBARI-12503.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)