ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-16251) Hive metastore alerts are present after upgrade/downgrade and enabling security
Date Wed, 04 May 2016 21:01:13 GMT

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

Hudson commented on AMBARI-16251:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #4792 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4792/])
AMBARI-16251. Hive metastore alerts are present after upgrade/downgrade (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=22988751d981abb48f9bc80c4f8536a9cded366f])
* ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py
* ambari-server/src/test/python/stacks/2.1/HIVE/test_hive_metastore.py


> Hive metastore alerts are present after upgrade/downgrade and enabling security
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-16251
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16251
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16251.patch
>
>
> The cause of this bug is not obvious.  In the upgrade/downgrade cycle for HDP-2.2 upgrade
to HDP-2.4 downgrade to HDP-2.2, the Metastore upgrade_schema method will invoke configure().
 This in turn creates (correctly) {{/usr/hdp/current/hive-metastore/conf/conf.server}} to
place configs.  The bug is that upgrade_schema happens BEFORE hdp-select is called, so the
directory is created within HDP-2.2.  Then on downgrade, that directory is left intact.
> The alert checks for existence of {{conf/conf.server}} as an indication of where to look
for configs.  Since that directory is incorrect for HDP-2.2, the wrong configs are loaded
when running the alert script.  This is an issue when security is enabled since the wrong
configs are now checked.
> The fix is to invoke upgrade_schema AFTER hdp-select instead of before.  That way, the
{{conf/conf.server}} directory is created in the correct directory in the version that supports
it.



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

Mime
View raw message