ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xun REN (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21294) Setup should keep existing connection-pool setting in ambari.properties
Date Mon, 18 Sep 2017 15:43:00 GMT

    [ 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)

Mime
View raw message