In such a small cluster I'd definitely consider doubling up masters and tservers on all of the master nodes (ie 3 masters and 5 tservers). The master is pretty light weight and can be colocated with tservers for such a small workload. This way you'll get better fault tolerance and also better performance vs using 2/5 of the nodes mostly unutilized.   -Todd ... View more

Hi, There is not a command to do this. However, if you are using Cloudera Manager, you can navigate to the "Charts Library" page under the Kudu service, and then select "Tables" on the left hand side, and then select the table of interest. This should give various metrics including its size on disk (post-replication). Hope that helps -Todd ... View more

It looks like your screenshot is of the "scans" dashboard on the web UI. This dashboard shows counters for a single scan, and a single scan would only come from a single task, not aggregate across them. I am guessing you're hitting KUDU-2231, a performance bug recently fixed. The bug fix appears in CDH 5.14.0. Since this is a performance issue that is not a regression and does not affect correctness, we have not yet backported to any prior releases. -Todd ... View more

That's correct, I am not aware of a workaround for this issue. ... View more

Hi, Unfortunately the Kudu client is built in such a way that it requires SSE4.2. The CPU you are running on was discontinued in Q4 2010 and not supported by Kudu. That includes the Kudu client which is used by Impala. Unfortunately you will not be able to query Kudu tables in a mixed cluster with impala daemons that do not support SSE4.2. -Todd ... View more

Hi, If you simply increase your timeout, the client itself has built-in retries and will keep trying to complete the insert until the given time has elapsed. In a scenario that is not latency-sensitive I would recommend increasing the timeout to a minute or two. -Todd ... View more

You could use 'tinker step 500' and have the effect that stepping would only be enabled for time differences more than 500ms. I wouldn't consider this breaking your production environment, but I guess you may have some reason that '-x' is important to you. We'll work on addressing this in a future release so that no system-wide changes are necessary. -Todd ... View more