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 "Sahil Takiar (Jira)" <ji...@apache.org> on 2019/09/19 23:10:00 UTC
[jira] [Resolved] (IMPALA-8634) Catalog client should be resilient
to temporary Catalog outage
[ https://issues.apache.org/jira/browse/IMPALA-8634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sahil Takiar resolved IMPALA-8634.
----------------------------------
Fix Version/s: Impala 3.4.0
Resolution: Fixed
> Catalog client should be resilient to temporary Catalog outage
> --------------------------------------------------------------
>
> Key: IMPALA-8634
> URL: https://issues.apache.org/jira/browse/IMPALA-8634
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Affects Versions: Impala 3.2.0
> Reporter: Michael Ho
> Assignee: Sahil Takiar
> Priority: Critical
> Fix For: Impala 3.4.0
>
>
> Currently, when the catalog server is down, catalog clients will fail all RPCs sent to it. In essence, DDL queries will fail and the Impala service becomes a lot less functional. Catalog clients should consider retrying failed RPCs with some exponential backoff in between while catalog server is being restarted after crashing. We probably need to add [a test |https://github.com/apache/impala/blob/master/tests/custom_cluster/test_restart_services.py] to exercise the paths of catalog restart to verify coordinators are resilient to it.
> cc'ing [~stakiar], [~joemcdonnell], [~twm378]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org