tree bdb5b3283c7147af31e625a7404f1b8fc6b40408
parent 88dcdfd4662d0ec4a6e0d81d643d207f6e5ed900
author stiga-huang <huangquanlong@gmail.com> 1710327029 +0800
committer Impala Public Jenkins <impala-public-jenkins@cloudera.com> 1711432492 +0000

IMPALA-12699: Set timeout for catalog RPCs

We have seen trivial GetPartialCatalogObject RPCs hanging in coordinator
side, e.g. IMPALA-11409. Due to the piggyback mechanism of fetching
metadata in local-catalog mode (see comments in
CatalogdMetaProvider#loadWithCaching()), a hanging RPC on shared
metadata (e.g. db/table list) could block other queries on the same
coordinator.

Such lightweight requests don't need to acquire table lock or trigger
table loading in catalogd. The causes of the hanging are usually
network issues, e.g. TCP connection become half open due to TCP
retransmissions timed out. A retry on the RPC helps to recover from such
failures. Currently, the timeout for catalog RPC is set to 0 by default.
This prevent the retry and let the client to wait infinitely.

This patch distinguishes the lightweight catalog RPCs and uses a
dedicated catalogd client cache for them. They use a timeout of 30 mins
which is longer enough to tolerate TCP retransmission timeouts.
Also sets a timeout of 10 hours for other catalog RPCs. Operations take
longer than that are usually abnormal and hanging.

Tests
 - Add e2e test to verify the lightweight RPC client cache is used.
 - Adjust TestRestart.test_catalog_connection_retries to use local
   catalog mode since in the legacy catalog mode, coordinator only sends
   PrioritizeLoad requests which are lightweight RPCs.

This is a continuation of patch by Wenzhe Zhou <wzhou@cloudera.com>

Change-Id: Iad39a79d0c89f2b04380f610a7e60558429e9c6e
Reviewed-on: http://gerrit.cloudera.org:8080/21146
Reviewed-by: Wenzhe Zhou <wzhou@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>