Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Kudu: partitioning strategy for performance related to number of disks

Kudu: partitioning strategy for performance related to number of disks

New Contributor

The documentation says:

It is recommended that new tables which are expected to have heavy read and write workloads have at least as many tablets as tablet servers.

If I have as many tablets as data disks (for instance 3 tablet servers, 10 disks per node, I split the table in 30 partitions), will kudu be smart enough to put a tablet per disk or am I actually limiting performance?

I wonder in theory (assuming a very big table) what would be the best:

  • 3 partitions (1 per tablet server),
  • 30 partitions (1 per disk),
  • More than 30 (because my table is really big),
  • Something in between?
Don't have an account?
Coming from Hortonworks? Activate your account here