[
https://issues.apache.org/jira/browse/HIVE-19994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815482#comment-16815482
]
Hrishi commented on HIVE-19994:
-------------------------------
We had the same issue in one of our environment,
*In Impala logs,*
11:10:28.051355 4188 catalog-server.cc:70] ImpalaRuntimeException: Error
making 'dropTable' RPC to Hive Metastore:
CAUSED BY: MetaException: One or more instances could not be deleted
*In Metastore logs*
java.sql.BatchUpdateException: Cannot delete or update a parent row: a foreign
key constraint fails ("HMS_abfgdffhsdhyshs"."COLUMNS_V2", CONSTRAINT
"COLUMNS_V2_FK1" FOREIGN KEY ("CD_ID") REFERENCES "CDS" ("CD_ID"))
Caused by:
com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
Cannot delete or update a parent row: a foreign key constraint fails
("HMS_abfgdffhsdhyshs"."COLUMNS_V2", CONSTRAINT "COLUMNS_V2_FK1" FOREIGN KEY
("CD_ID") REFERENCES "CDS" ("CD_ID"))
We noticed that there was a long-running query being run on the HMS that
resulted in higher CPU utilization on the database and this seems to have
exacerbated the mentioned bug where a slightly degraded HMS performance
resulted in drop tables/views not working to a higher occurrence. Following the
termination of the query, we are seeing the drop table/view returning to normal.
Could you have a review of how the logic handles instances where the hive
metastore performance is degraded slightly?
> Impala "drop table" fails with Hive Metastore exception
> -------------------------------------------------------
>
> Key: HIVE-19994
> URL: https://issues.apache.org/jira/browse/HIVE-19994
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 1.1.0
> Environment: Hadoop distribution: CHD 5.14.2
> Hive version: 1.1.0-cdh5.14.2
> Impala version: 2.11.0
> Kudu version: 1.6.0
>
> Reporter: Rodion Myronov
> Priority: Major
> Attachments: metastore_exception.txt
>
>
> "drop table" statement in Impala shell fails with the following exception:
> {{ImpalaRuntimeException: Error making 'dropTable' RPC to Hive Metastore:
> CAUSED BY: MetaException: One or more instances could not be deleted}}
>
> Metastore log file shows that "DELETE FROM `PARTITION_KEYS` WHERE `TBL_ID`=?"
> statement fails because of foreign key violation (full stacktrace will be
> added):
> {{Caused by: java.sql.BatchUpdateException: Cannot delete or update a parent
> row: a foreign key constraint fails
> ("hivemetastore_emtig3vtq7qp1tiooo07sb70ud"."COLUMNS_V2", CONSTRAINT
> "COLUMNS_V2_FK1" FOREIGN KEY ("CD_ID") REFERENCES "CDS" ("CD_ID"))}}
>
> The table is created and then dropped as a part of ETL process executed every
> hour. Most of the time it works fine, the issue is not reproducible at will.
> Table creation script is:
> {{CREATE TABLE IF NOT EXISTS price_advisor_ouput.t_switching_coef_source}}
> {{( }}
> {{...fields here...}}
> {{PRIMARY KEY (...PK field here...)}}
> {{)}}
> {{PARTITION BY HASH(matrix_pcd) PARTITIONS 3}}
> {{STORED AS KUDU;}}
>
> Not sure how to approach diagnostics and fix, so any input will be really
> appreciated.
> Thanks in advance,
> Rodion Myronov
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
