You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2017/06/22 15:21:00 UTC
[jira] [Commented] (AMBARI-21294) Setup should keep existing
connection-pool setting in ambari.properties
[ https://issues.apache.org/jira/browse/AMBARI-21294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059522#comment-16059522 ]
Hudson commented on AMBARI-21294:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1623 (See [https://builds.apache.org/job/Ambari-branch-2.5/1623/])
AMBARI-21294. Setup should keep existing connection-pool setting in (adoroszlai: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f6bd2b9077922f11507bda54777b8b56188cb3ed])
* (edit) ambari-server/src/main/python/ambari_server/dbConfiguration_linux.py
> Setup should keep existing connection-pool setting in ambari.properties
> -----------------------------------------------------------------------
>
> Key: AMBARI-21294
> URL: https://issues.apache.org/jira/browse/AMBARI-21294
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.2
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21294.patch
>
>
> {{ambari-server setup --database}} always updates {{server.jdbc.connection-pool}} based on database type: {{c3p0}} for MySQL, {{internal}} for all other RDMBS types. It should force {{c3p0}} for MySQL, but should retain any existing setting for others.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)