[jira] [Commented] (AMBARI-13238) MySQL service check needs to be more robust

["Thomas Friedrich (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907343#comment-14907343 ] 

Thomas Friedrich commented on AMBARI-13238:
-------------------------------------------

The proposed patch checks for the pid file location as configured in /etc/my.cnf which is the default config location for MySQL server. Since the MySQL server instance in Ambari doesn't set the config location, it will use the values configured in the default config file. The status command will then check for the process with the id referenced in the pid file.

> MySQL service check needs to be more robust
> -------------------------------------------
>
>                 Key: AMBARI-13238
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13238
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0, 2.1.0
>            Reporter: Thomas Friedrich
>            Assignee: Thomas Friedrich
>            Priority: Minor
>         Attachments: AMBARI-13238.patch
>
>
> The mysql service check in mysql_service.py simply checks for the existence of a mysqld process. If an unrelated mysqld service is running on the same node and Hive is configured to run with a MySQL db, the Hive start action won't start the MySQL server instance and the metastore connection fails.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)