You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2017/04/11 00:15:41 UTC

[jira] [Created] (KUDU-1967) Umbrella JIRA for node density improvements

Adar Dembo created KUDU-1967:
--------------------------------

             Summary: Umbrella JIRA for node density improvements
                 Key: KUDU-1967
                 URL: https://issues.apache.org/jira/browse/KUDU-1967
             Project: Kudu
          Issue Type: Task
          Components: fs, master, tablet, tserver
    Affects Versions: 1.3.0
            Reporter: Adar Dembo
            Assignee: Adar Dembo


For the Kudu 1.4 release, I'll be working to improve node density.

Here's a brief primer on Kudu's scalability targets today:
# We recommend no more than 4 TB of total data per node. This is specific to Kudu data blocks, so this data is post-encoding and post-compression.
# We recommend no more than 1000 partitions (post-replication) per node.
# We recommend no more than 100 nodes per cluster.
# We recommend no more than 60 partitions per table per tserver.

For 1.4, here's what we'd like to achieve:
# Up to 16 TB of total data per node. Maybe even 48 TB, if possible.
# Up to 100 "hot" partitions per node. In this context, "hot" means partitions that are actively servicing writes.
# Thousands of "cold" partitions per node. Put another way, it should be drastically cheaper to serve "cold" partitions than it is today.
# Maintain the "100 nodes per cluster" limit.
# Remove the "no more than 60 partitions per table per node" limit.

I'll be linking various interesting JIRAs into this one, and I'll document, for each one, which aspect of data scalability it affects.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)