[
https://issues.apache.org/jira/browse/IMPALA-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Quanlong Huang updated IMPALA-14958:
------------------------------------
Description:
Some ExecNode implementations don't invoke
[ScopedOpenEventAdder|https://github.com/apache/impala/blob/a44f72d8f80677509a98439a5b46fa2cbb933db7/be/src/exec/exec-node-util.h#L31]
and
[ScopedGetNextEventAdder|https://github.com/apache/impala/blob/a44f72d8f80677509a98439a5b46fa2cbb933db7/be/src/exec/exec-node-util.h#L50],
which leads to weird timelines in the profile that just have the "Closed"
event. KuduScanNodeMt is an example.
KuduScanNodeMt (MT_DOP>0)
{noformat}
KUDU_SCAN_NODE (id=0):
Table Name: functional_kudu.alltypes
Node Lifecycle Event Timeline: 13.588ms
- Closed: 13.588ms (13.588ms){noformat}
KuduScanNode (MT_DOP=0) is fine.
{noformat}
KUDU_SCAN_NODE (id=0):
Table Name: functional_kudu.alltypes
Node Lifecycle Event Timeline: 26.370ms
- Open Started: 15.425ms (15.425ms)
- Open Finished: 22.982ms (7.557ms)
- First Batch Requested: 22.987ms (5.073us)
- First Batch Returned: 26.349ms (3.361ms)
- Last Batch Returned: 26.351ms (1.838us)
- Closed: 26.370ms (18.892us){noformat}
IcebergMetadataScanNode and SystemTableScanNode also have this issue:
{noformat}
Sql Statement: select * from
functional_parquet.iceberg_query_metadata.entries
ICEBERG_METADATA_SCAN_NODE (id=0):
Node Lifecycle Event Timeline: 213.956ms
- Closed: 213.956ms (213.956ms)
Sql Statement: select * from sys.impala_query_live
SYSTEM_TABLE_SCAN_NODE (id=0):
Node Lifecycle Event Timeline: 16.510ms
- Closed: 16.510ms (16.510ms){noformat}
This is misleading for HBO to check whether the node actually completes.
was:
Some ExecNode implementations don't invoke
[ScopedOpenEventAdder|https://github.com/apache/impala/blob/a44f72d8f80677509a98439a5b46fa2cbb933db7/be/src/exec/exec-node-util.h#L31]
and
[ScopedGetNextEventAdder|https://github.com/apache/impala/blob/a44f72d8f80677509a98439a5b46fa2cbb933db7/be/src/exec/exec-node-util.h#L50],
which leads to weird timelines in the profile that just have the "Closed"
event. KuduScanNodeMt is an example.
KuduScanNodeMt (MT_DOP>0)
{noformat}
KUDU_SCAN_NODE (id=0):
Table Name: functional_kudu.alltypes
Node Lifecycle Event Timeline: 13.588ms
- Closed: 13.588ms (13.588ms){noformat}
KuduScanNode (MT_DOP=0) is fine.
{noformat}
KUDU_SCAN_NODE (id=0):
Table Name: functional_kudu.alltypes
Node Lifecycle Event Timeline: 26.370ms
- Open Started: 15.425ms (15.425ms)
- Open Finished: 22.982ms (7.557ms)
- First Batch Requested: 22.987ms (5.073us)
- First Batch Returned: 26.349ms (3.361ms)
- Last Batch Returned: 26.351ms (1.838us)
- Closed: 26.370ms (18.892us){noformat}
IcebergMetadataScanNode and SystemTableScanNode also have this issue:
{noformat}
Sql Statement: select * from
functional_parquet.iceberg_query_metadata.entries
ICEBERG_METADATA_SCAN_NODE (id=0):
Node Lifecycle Event Timeline: 213.956ms
- Closed: 213.956ms (213.956ms){noformat}
Sql Statement: select * from sys.impala_query_live
SYSTEM_TABLE_SCAN_NODE (id=0):
Node Lifecycle Event Timeline: 16.510ms
- Closed: 16.510ms (16.510ms){noformat}
This is misleading for HBO to check whether the node actually completes.
> Missing Node Lifecycle Events in some ExecNodes
> -----------------------------------------------
>
> Key: IMPALA-14958
> URL: https://issues.apache.org/jira/browse/IMPALA-14958
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Reporter: Quanlong Huang
> Assignee: Quanlong Huang
> Priority: Critical
>
> Some ExecNode implementations don't invoke
> [ScopedOpenEventAdder|https://github.com/apache/impala/blob/a44f72d8f80677509a98439a5b46fa2cbb933db7/be/src/exec/exec-node-util.h#L31]
> and
> [ScopedGetNextEventAdder|https://github.com/apache/impala/blob/a44f72d8f80677509a98439a5b46fa2cbb933db7/be/src/exec/exec-node-util.h#L50],
> which leads to weird timelines in the profile that just have the "Closed"
> event. KuduScanNodeMt is an example.
> KuduScanNodeMt (MT_DOP>0)
> {noformat}
> KUDU_SCAN_NODE (id=0):
> Table Name: functional_kudu.alltypes
> Node Lifecycle Event Timeline: 13.588ms
> - Closed: 13.588ms (13.588ms){noformat}
> KuduScanNode (MT_DOP=0) is fine.
> {noformat}
> KUDU_SCAN_NODE (id=0):
> Table Name: functional_kudu.alltypes
> Node Lifecycle Event Timeline: 26.370ms
> - Open Started: 15.425ms (15.425ms)
> - Open Finished: 22.982ms (7.557ms)
> - First Batch Requested: 22.987ms (5.073us)
> - First Batch Returned: 26.349ms (3.361ms)
> - Last Batch Returned: 26.351ms (1.838us)
> - Closed: 26.370ms (18.892us){noformat}
> IcebergMetadataScanNode and SystemTableScanNode also have this issue:
> {noformat}
> Sql Statement: select * from
> functional_parquet.iceberg_query_metadata.entries
> ICEBERG_METADATA_SCAN_NODE (id=0):
> Node Lifecycle Event Timeline: 213.956ms
> - Closed: 213.956ms (213.956ms)
> Sql Statement: select * from sys.impala_query_live
> SYSTEM_TABLE_SCAN_NODE (id=0):
> Node Lifecycle Event Timeline: 16.510ms
> - Closed: 16.510ms (16.510ms){noformat}
> This is misleading for HBO to check whether the node actually completes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
