Michael Ho created KUDU-2237:
--------------------------------
Summary: Allows idle server connection detection to be disabled
Key: KUDU-2237
URL: https://issues.apache.org/jira/browse/KUDU-2237
Project: Kudu
Issue Type: Bug
Components: rpc
Affects Versions: 1.5.0
Reporter: Michael Ho
Assignee: Michael Ho
Priority: Minor
As shown in IMPALA-5901, Impala server connections between backends can be idle
for an extended period of time during stress or when the cluster is idle. Given
Impalad cluster tends to have n^2 connections (i.e. fully connected between all
backend nodes), shutting down idle connections may easily result in a
connection storm in which all nodes try to connect to each other at the same
time. This is somewhat worse in a secure cluster due to the higher overhead in
connection negotiation. We don't necessarily benefit much from closing idle
connections so it'd be nice to allow us to disable it if we want. Currently, we
workaround the issue by setting {{rpc_default_keepalive_time_ms}} to a very
large number. Given the value 0 for {{rpc_default_keepalive_time_ms}} isn't too
meaningful, we can consider using setting{{rpc_default_keepalive_time_ms}} to 0
as way to disable the idle server connection scanning.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
