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

Sergio Peña commented on HIVE-13507:
------------------------------------

I see many issues are metastore connection errors, and this is the culprit of 
everything:

{noformat}
Caused by: java.sql.SQLException: Failed to create database 
'/home/hiveptest/54.177.132.113-hiveptest-1/apache-github-source-source/itests/hive-unit/target/tmpTestFilterHooksmetastore_db',
 see the next exception for details.
        at 
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at 
org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
 Source)
        ... 58 more
Caused by: java.sql.SQLException: The database directory 
'/home/hiveptest/54.177.132.113-hiveptest-1/apache-github-source-source/itests/hive-unit/target/tmpTestFilterHooksmetastore_db'
 exists. However, it does not contain the expected 'service.properties' file. 
Perhaps Derby was brought down in the middle of creating this database. You may 
want to delete this directory and try creating the database again.
{noformat}

I deleted the directory directly on the slave, and the test now passes. I'd 
like to create a Jira to fix this, but I don't know if its a ptest or another 
test that is corrupting the metastore. 

> Improved logging for ptest
> --------------------------
>
>                 Key: HIVE-13507
>                 URL: https://issues.apache.org/jira/browse/HIVE-13507
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>             Fix For: 2.1.0
>
>         Attachments: HIVE-13507.01.patch, HIVE-13507.02.patch
>
>
> NO PRECOMMIT TESTS
> Include information about batch runtimes, outlier lists, host completion 
> times, etc. Try identifying tests which cause the build to take a long time 
> while holding onto resources.



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

Reply via email to