You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2023/03/23 17:38:00 UTC
[jira] [Created] (IMPALA-12024) For CTAS, include time to create the table in the query profile timeline
Joe McDonnell created IMPALA-12024:
--------------------------------------
Summary: For CTAS, include time to create the table in the query profile timeline
Key: IMPALA-12024
URL: https://issues.apache.org/jira/browse/IMPALA-12024
Project: IMPALA
Issue Type: Improvement
Components: Backend
Affects Versions: Impala 4.3.0
Reporter: Joe McDonnell
If the metastore is slow, catalog operations to create / drop tables can take a long time. For a CTAS statement, we don't have a clear indication in the profile that this is happening. Instead, it shows up as a gap between planning finished and submitting for admission:
{noformat}
Query Timeline: 12s696ms
- Query submitted: 64.303us (64.303us)
- Planning finished: 117.816ms (117.752ms)
- Submit for admission: 12s360ms (12s243ms)
...{noformat}
This may apply for other statement types.
To reproduce with CTAS on an Impala devenv:
{noformat}
1. Start Impala
2. In impala-shell, run "select * from functional.alltypes"
3. Find the metastore pid (jps -v | grep metastore)
4. sudo gdb attach ${metastore_pid}
5. In impala-shell, run "create table foo as select * from functional.alltypes"
.. This will hang because it can't create the table, wait a bit
6. Back in the gdb session, detach from metastore and let the CTAS finish{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org