[
https://issues.apache.org/jira/browse/AMBARI-21555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097091#comment-16097091
]
Hudson commented on AMBARI-21555:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1737 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1737/])
AMBARI-21555 Hive restart fails to restart MySQL after Ambari upgrade (dili:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=61df6972d3105baf2dd7718fe0d26c711d23beed])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog252.java
> 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)
