[
https://issues.apache.org/jira/browse/IMPALA-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521591#comment-17521591
]
ASF subversion and git services commented on IMPALA-7168:
---------------------------------------------------------
Commit e530f6a9ced62613c067a9ae30bac7438bffd3fc in impala's branch
refs/heads/master from Fang-Yu Rao
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=e530f6a9c ]
IMPALA-11236: Upgrade ehcache sizeof library to 0.4.0
It was found that the ehcache sizeof (version 0.3.0) library used by
CatalogdMetaProvider can fail due to an InaccessibleObjectException
during reflection and cause the impalad to stuck during startup
indefinitely. This could trigger IMPALA-7168 which affects sync_ddl
queries running on unaffected impalads.
This patch upgrades the version of the ehcache sizeof library so that
the exception could be handled within the ehcache sizeof library after
the upgrade.
Testing:
- Verified that the patch passes Impala's core tests.
Change-Id: I853264684aa2ba9c3743f9e53bd52fa2752a45a1
Reviewed-on: http://gerrit.cloudera.org:8080/18400
Reviewed-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Quanlong Huang <[email protected]>
Tested-by: Quanlong Huang <[email protected]>
> DML query may hang if CatalogUpdateCallback() encounters repeated error
> -----------------------------------------------------------------------
>
> Key: IMPALA-7168
> URL: https://issues.apache.org/jira/browse/IMPALA-7168
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 2.9.0, Impala 2.10.0, Impala 2.11.0, Impala 3.0,
> Impala 2.12.0
> Reporter: Pranay Singh
> Priority: Major
>
> DML queries or INSERT will encounter a hang, if
> exec_env_->frontend()->UpdateCatalogCache() in
> ImpalaServer::CatalogUpdateCallback encounters repeated error like ENOMEM.
> This happens with SYNC_DDL set to 1 when the coordinator node is waiting for
> it's catalog version to become current.
> The scenario shows up like this, lets say there are two coordinator nodes ,
> Node A, Node B
> and catalogd and statestored are running on Node C.
> a) CREATE TABLE is executed on Node A, with SYNC_DDL set to 1, the thread
> running the query is going to block in
> impala::ImpalaServer::ProcessCatalogUpdateResult(), waiting for it's catalog
> version to become current.
> b) Meanwhile statestored running on Node C would call
> ImpalaServer::CatalogUpdateCallback on Node B via thrift RPC to do a delta
> topic update, which would not happen if we encounter repeated errors, say
> front end is low on memory (low JVM heap situation).
> c) In such case Node A will wait indefinitely waiting for it's catalog
> version to become current, till Node B is shutdown voluntarily.
> Note: This is a case where Node B is reachable (hearbeat is fine, but node is
> in a bad state, non working).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
