You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/10/16 23:11:05 UTC

[jira] [Commented] (AMBARI-13459) Hive Metastore Upgrade Retry Fails Because Of Driver Copy Issue

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

Hadoop QA commented on AMBARI-13459:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12767104/AMBARI-13459.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/3991//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3991//console

This message is automatically generated.

> Hive Metastore Upgrade Retry Fails Because Of Driver Copy Issue
> ---------------------------------------------------------------
>
>                 Key: AMBARI-13459
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13459
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Blocker
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13459.patch
>
>
> *Problem:* During Rolling Upgrade, if Hive Metastore fails to restart, even after clicking *Retry*, Ambari cannot restart Hive Metastore. This situation can occur if Hive Metastore is using an external database (such as Oracle).
> *Solution:* During Rolling Upgrade, if Hive Metastore fails to restart, even after clicking *Retry* in the Rolling Upgrade Wizard, Ambari cannot restart Hive Metastore and displays the following error in Ambari:
> {code}
> resource_management.core.exceptions.Fail: Execution of 'cp /usr/hdp/current/hive-metastore/lib/ojdbc.jar /usr/hdp/2.3.2.0-2943/hive/lib' returned 1. cp: '/usr/hdp/current/hive-metastore/lib/ojdbc.jar' and '/usr/hdp/2.3.2.0-2943/hive/lib/ojdbc.jar' are the same file
> {code}
> In order to get Hive Metastore to restart, before clicking *Retry* again, go onto the Hive Metastore host and move HDP version back to the original.
> {code}
> hdp-select set hive-metastore <original-hdp-version>
> {code}
> After performing the hdp-select, click *Retry* and proceed with the Rolling Upgrade.



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