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

Add a way to set Kudu client's rpc_max_message_size via KuduClientBuilder

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.17.0
    • 1.18
    • client
    • None

    Description

      In some Impala workloads, we have seen issues fetching data from Kudu, because the RPC message size exceeds the rpc_max_message_size for the Kudu client (which defaults to 50MB). This is likely due to very large strings or binary data. See IMPALA-13202.

      We should add a way to tune the rpc_max_message_size for the Kudu client. In discussions on IMPALA-13202, the option we preferred is to add a way to specify this on the KuduClientBuilder (similar to how we handle num_reactors today).

       

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. IMPALA-13202 Impala workloads can exceed Kudu client's rpc_max_message_size limit

          • Critical - Crashes, loss of data, severe memory leak.
          • Open

          Activity

            People

              araina Ashwani Raina
              joemcdonnell Joe McDonnell
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: