Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-2237

Allows idle server connection detection to be disabled

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 1.5.0
    • 1.7.0
    • rpc
    • None

    Description

      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 using a very large value for rpc_default_keepalive_time_ms. 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.

      Attachments

        Issue Links

          Activity

            People

              kwho Michael Ho
              kwho Michael Ho
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: