[
https://issues.apache.org/jira/browse/IMPALA-12655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798849#comment-17798849
]
Quanlong Huang commented on IMPALA-12655:
-----------------------------------------
The wrong db name is just a bug of the error message in Hive. We can ignore it.
[https://github.com/apache/hive/blob/4a057a7cea11029dbda7adaec09117d46e56d925/standalone-metastore/metastore-server/src/main/java/org/apache/hadoop/hive/metastore/MetastoreDefaultTransformer.java#L775]
{code:java}
private Database getDbForTable(Table oldTable) throws MetaException {
try {
return hmsHandler.get_database_core(oldTable.getCatName(),
oldTable.getDbName());
} catch (NoSuchObjectException e) {
throw new MetaException(
"Database " + oldTable.getTableName() + " for table " +
oldTable.getTableName() + " could not be found");
}
} {code}
The failure of getting the db is due to HMS timeout to fetch metadata from the
underlying RDBMS:
{noformat}
2023-12-18T12:38:11,788 ERROR [TThreadPoolServer WorkerProcess-191]
metastore.ObjectStore:
javax.jdo.JDODataStoreException: objectstore - Connection is not available,
request timed out after 30000ms.
...
2023-12-18T12:38:11,792 WARN [TThreadPoolServer WorkerProcess-191]
metastore.ObjectStore: Failed to get database
hive.tpcds_partitioned_parquet_snap, returning NoSuchObjectException
org.apache.hadoop.hive.metastore.api.MetaException: objectstore - Connection is
not available, request timed out after 30000ms.{noformat}
Maybe the underlying RDBMS is just too busy. I think it's something we need to
fix in HMS side.
> PlannerTest.testProcessingCost seems flaky
> ------------------------------------------
>
> Key: IMPALA-12655
> URL: https://issues.apache.org/jira/browse/IMPALA-12655
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Reporter: Csaba Ringhofer
> Priority: Major
> Attachments:
> catalogd.impala-ec2-centos79-m6i-4xlarge-ondemand-02f3.vpc.cloudera.com.jenkins.log.INFO.20231218-120036.29228.tgz,
> compute-table-stats.log, hive-metastore.log.tgz,
> impalad.impala-ec2-centos79-m6i-4xlarge-ondemand-02f3.vpc.cloudera.com.jenkins.log.INFO.20231218-120036.29280.tgz
>
>
> This is probably caused by IMPALA-12601
> https://github.com/apache/impala/commit/8661f922d3ccb21da73b9f7f8734d9113429e9bb
> The error was cause by this line:
> https://github.com/apache/impala/blob/68fe57ff8492a7afdf14a62cabd3e2b0fcade9d1/testdata/workloads/functional-planner/queries/PlannerTest/tpcds-processing-cost.test#L8185
> In the actual plan the following appeared here:
> fk/pk conjuncts: assumed fk/pk
> [~rizaon]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
