[
https://issues.apache.org/jira/browse/IMPALA-12809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Becker updated IMPALA-12809:
-----------------------------------
Summary: Iceberg metadata table scanner should always be scheduled to the
coordinator (was: Iceberg metadata table scanner can be scheduled to executors)
> Iceberg metadata table scanner should always be scheduled to the coordinator
> ----------------------------------------------------------------------------
>
> Key: IMPALA-12809
> URL: https://issues.apache.org/jira/browse/IMPALA-12809
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 4.4.0
> Reporter: Tamas Mate
> Assignee: Daniel Becker
> Priority: Major
> Labels: impala-iceberg
>
> On larger clusters the Iceberg metadata scanner can be scheduled to
> executors, for example during a join. The fragment in this case will fail a
> precondition check, because either the frontend_ object will not be present
> or the table. Setting {{exec_at_coord}} to true is not enough and these
> fragments should be scheduled to the {{{}coord_only_executor_group{}}}.
> Additionally, setting NUM_NODES=1 should be a viable workaround.
> Reproducible with the following local dev Impala cluster:
> {{./bin/start-impala-cluster.py --cluster_size=3 --num_coordinators=1
> --use_exclusive_coordinators}}
> and query:
> {{select count(b.parent_id) from
> functional_parquet.iceberg_query_metadata.history a}}
> {{join functional_parquet.iceberg_query_metadata.history b on a.snapshot_id =
> b.snapshot_id;}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
