[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=14947870#comment-14947870 ] 

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

Changed the patch. Instead of relying on the cnf file location (which can be in different places), use the "mysqladmin variables" command to get the pid file location. The Hive MySQL server instance is started without passing in any parameters to overwrite the cnf location, and any other MySQL instance that is running on the machine needs to be started with explicitly specifying a different set of config values, as it wouldn't be able to run otherwise. Hence just running mysqladmin will return the values for the Hive MySQL instance.

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