You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Xun REN (JIRA)" <ji...@apache.org> on 2017/09/18 15:43: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=16170166#comment-16170166 ]
Xun REN commented on AMBARI-21294:
----------------------------------
Hello,
We have a big slowness on Ambari server(maily because of Ambari metrics). I am asking self if it is related to the DB connection pool. May I know why we should use "internal" connection pool for the DB type other than "MySQL" ? How is the "internal" connection pool managed ?
Thanks in advance!
> 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)