ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12391) Rolling upgrade failed on Hive restart for Centos 7
Date Sun, 12 Jul 2015 23:13:04 GMT

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

Hadoop QA commented on AMBARI-12391:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12744954/AMBARI-12391.2.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/3396//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3396//console

This message is automatically generated.

> Rolling upgrade failed on Hive restart for Centos 7
> ---------------------------------------------------
>
>                 Key: AMBARI-12391
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12391
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-12391.2.patch, AMBARI-12391.patch
>
>
> It's a Metastore restart failure
> {code}
> 2015-07-09 18:10:15,641 - Executing Metastore Rolling Upgrade pre-restart
> 2015-07-09 18:10:15,643 - Upgrading Hive Metastore
> 2015-07-09 18:10:15,645 - Execute['('cp', '/usr/hdp/current/hive-metastore/lib/mysql-connector-java.jar',
u'/usr/hdp/2.3.0.0-2545/hive/lib')'] {'path': ['/bin', '/usr/bin/'], 'sudo': True}
> 2015-07-09 18:10:15,682 - Execute['/usr/hdp/2.3.0.0-2545/hive/bin/schematool -dbType
mysql -upgradeSchema'] {'logoutput': True, 'environment': {'HIVE_CONF_DIR': '/usr/hdp/current/hive-metastore/conf/conf.server'},
'tries': 1, 'user': 'hive'}
> WARNING: Use "yarn jar" to launch YARN applications.
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to load driver
> *** schemaTool failed ***
> {code}
> When I tried a dryrun,
> {code}
> sudo -u hive /usr/hdp/2.3.0.0-2545/hive/bin/schematool -dryRun -dbType mysql -upgradeSchema
> {code}
> it doesn't seem to fail on the driver load issue, though it was failing on something
else.
> I am assuming this is related to us missing some libraries during rolling-upgrades.
> But we need to find out what exactly it is that is missing. Is it mysql-connector-java.jar
? Does it need to be readable by hive user, given the ugpradeSchema command above is running
as hive?
> {code}
> # ls -l /usr/hdp/2.3.0.0-2545/hive/lib/mysql-connector-java.jar
> -rw-r-----. 1 root root 959987 Jul  9 18:10 /usr/hdp/2.3.0.0-2545/hive/lib/mysql-connector-java.jar
> {code}



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

Mime
View raw message