ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Di Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-21555) Hive restart fails to restart MySQL after Ambari upgrade against IOP 4.2.5
Date Fri, 21 Jul 2017 20:15:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-21555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Di Li updated AMBARI-21555:
---------------------------
    Attachment: AMBARI-21555.patch

> Hive restart fails to restart MySQL after Ambari upgrade against IOP 4.2.5
> --------------------------------------------------------------------------
>
>                 Key: AMBARI-21555
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21555
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.2
>            Reporter: Di Li
>            Assignee: Di Li
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21555.patch
>
>
> IOP uses MariaDB instead of MySQL when a cluster is on RedHat 7. HDP 2.6/Ambari 2.5.2
is yet to support MariaDB. A special flag is introduced to switch daemon type for migrated
clusters. Currently the flag is added during EU to handle both IOP 4.2 and 4.2.5. We also
need this flag to be added during Ambari upgrade for IOP 4.2.5 to restart MySQL ( IOP 4.2
is self-contained, thus not need this flag for restarting MySQL)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message