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 "Csaba Ringhofer (Jira)" <ji...@apache.org> on 2023/07/06 16:20:00 UTC
[jira] [Updated] (IMPALA-12267) DMLs/DDLs can hang as a result of catalogd change
[ https://issues.apache.org/jira/browse/IMPALA-12267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Csaba Ringhofer updated IMPALA-12267:
-------------------------------------
Affects Version/s:
:
Impala 2.8.0, Impala 3.2.0, Impala 4.0.0, Impala 3.3.0, Impala 3.4.0
> DMLs/DDLs can hang as a result of catalogd change
> -------------------------------------------------
>
> Key: IMPALA-12267
> URL: https://issues.apache.org/jira/browse/IMPALA-12267
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: :
Impala 2.8.0, Impala 3.2.0, Impala 4.0.0, Impala 3.3.0, Impala 3.4.0
> Reporter: Csaba Ringhofer
> 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 and cancelling the query also didn't help.
--
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