Is your cluster using Cloudera Manager for management? If so, have you configured a service dependency between Impala and Kudu? You'll need to go the CM configuration for Impala and reconfigure the Kudu dependency.   After you do that, CM will pass the right value for -kudu_master_hosts on the Impala command line when you next restart Impala, and you'll be able to create Kudu tables without explicitly specifying kudu.master_addresses. ... View more

As the a tserver approaches the memory limit, it'll apply backpressure on incoming writes, forcing them to slow down. This backpressure (and the limiting mechanism in general) is process-wide; there's no way to customize it for a particular tablet or memrowset.   If you let your write job run for a while, the memory usage should eventually stabilize. If it doesn't, please share a heap sample as per the instructions found here. ... View more

No, the rebalancer doesn't fix leader skew. It may in a future release. Leaders can cluster onto one tserver when individual tservers are restarted; if you restart the entire cluster all at once you might be able to redistribute leadership more evenly. You're right that if you're only using one host to initiate reads, the reads will go to the local tserver rather than round-robin across the cluster. The master doesn't directly tell where clients to scan; it just provides them with enough information to make that decision based on their replica selection policy. There's also no way to do round robin (or randomized) replica selection. ... View more