[
https://issues.apache.org/jira/browse/IMPALA-12267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Becker resolved IMPALA-12267.
------------------------------------
Resolution: Fixed
> DMLs/DDLs can hang as a result of catalogd restart
> --------------------------------------------------
>
> Key: IMPALA-12267
> URL: https://issues.apache.org/jira/browse/IMPALA-12267
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 4.2.0
> Reporter: Csaba Ringhofer
> Assignee: Daniel Becker
> Priority: Major
>
> IMPALA-5476 added handling for changes in catalogd service ID during the
> lifetime of a DML/DDL query, but the loop that waits for a new catalogd
> service ID can wait indefinitely in case the DML/DDL was handled by the
> previous catalogd and restart happened just after replying to the coordinator:
> https://github.com/apache/impala/blob/d0fe4c604f72d41019832513ebf65cfe8f469953/be/src/service/impala-server.cc#L2204
> Could reproduce this by adding a sleep just before taking
> catalog_version_lock_ and restarting catalogd while a DML/DDL was waiting
> there. As a result the query hanged - it could be finished only by restarting
> catalogd. Canncelling the query also wouldn't help, the thread that handles
> the query is stuck until catalogd restart.
> Note that this issue may be present on all Impala versions that contain
> IMPALA-5476, but I haven't verified this and other changes could also affect
> the behavior (e.g. async DML support).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
