You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2019/02/26 19:56:00 UTC

[jira] [Created] (KUDU-2711) Improve performance of GetTableLocations for large tables

Todd Lipcon created KUDU-2711:
---------------------------------

             Summary: Improve performance of GetTableLocations for large tables
                 Key: KUDU-2711
                 URL: https://issues.apache.org/jira/browse/KUDU-2711
             Project: Kudu
          Issue Type: Improvement
          Components: master, perf
    Affects Versions: 1.9.0
            Reporter: Todd Lipcon
            Assignee: Todd Lipcon


Currently the response for TableLocations returns a separate copy of the TSInfoPB for every replica. These PBs are relatively large and include string UUIDs, hostnames, etc. For large tables, a response may have up to 3000 replicas. In most clusters, the table itself will be on far fewer than 3000 unique hosts, so it makes sense to return the replicas as indexes into a response-level list rather than separately duplicate the TS info in each of the replica PBs.

Additionally, we can consider a reader-writer lock on TSDescriptor so that these requests can proceed more in parallel.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)