hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Gates (JIRA)" <>
Subject [jira] [Updated] (HIVE-8915) Log file explosion due to non-existence of COMPACTION_QUEUE table
Date Thu, 30 Apr 2015 22:29:06 GMT


Alan Gates updated HIVE-8915:
    Attachment: HIVE-8915.patch

This patch makes it so that the worker and cleaner don't go into a tight loop throwing errors.
 With this patch, if the transaction tables aren't in the database the logs are around 200K.

[~owen.omalley] suggested that we should make it so that the metastore died if the proper
tables weren't in place.  We could still do that, but I felt that was separate from this patch
because what this patch really fixed was making sure any error that occurred inside the compactor
threads didn't result in a tight loop. 

> Log file explosion due to non-existence of COMPACTION_QUEUE table
> -----------------------------------------------------------------
>                 Key: HIVE-8915
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 0.14.0, 0.15.0, 0.14.1
>            Reporter: Sushanth Sowmyan
>            Assignee: Alan Gates
>         Attachments: HIVE-8915.patch
> I hit an issue with a fresh set up of hive in a vm, where I did not have db tables as
specified by hive-txn-schema-0.14.0.mysql.sql created.
> On metastore startup, I got an endless loop of errors being populated to the log file,
which caused the log file to grow to 1.7GB in 5 minutes, with 950k copies of the same error
stack trace in it before I realized what was happening and killed it. We should either have
a delay of sorts to make sure we don't endlessly respin on that error so quickly, or we should
error out and fail if we're not able to start.
> The stack trace in question is as follows:
> {noformat}
> 2014-11-19 01:44:57,654 ERROR compactor.Cleaner
> ( - Caught an exception in the main loop of
> compactor cleaner, MetaException(message:Unable to connect to
> transaction database
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'hive.COMPACTION_QUEUE' doesn't exist
> at sun.reflect.GeneratedConstructorAccessor20.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
> at java.lang.reflect.Constructor.newInstance(
> at com.mysql.jdbc.Util.handleNewInstance(
> at com.mysql.jdbc.Util.getInstance(
> at com.mysql.jdbc.SQLError.createSQLException(
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(
> at com.mysql.jdbc.MysqlIO.sendCommand(
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(
> at com.mysql.jdbc.ConnectionImpl.execSQL(
> at com.mysql.jdbc.ConnectionImpl.execSQL(
> at com.mysql.jdbc.StatementImpl.executeQuery(
> at com.jolbox.bonecp.StatementHandle.executeQuery(
> at org.apache.hadoop.hive.metastore.txn.CompactionTxnHandler.findReadyToClean(
> at
> )
> at org.apache.hadoop.hive.metastore.txn.CompactionTxnHandler.findReadyToClean(
> at
> {noformat}

This message was sent by Atlassian JIRA

View raw message