@Braz wrote: Is there not a Kudu command which will allow for obtaining table size information? If not, then how does Cloudera Manager perform this? We would like to be able to replicate this behavior so that we can configure e-mail alerts to be sent whenever a table reaches a particular size.   Thanks, Braz     CM is scrapping and aggregating the /metrics pages from the tablet server instances for each tablet/table.   Have you reviewed CM triggers/alerts?[1] You might be able to configure email alerts with a similar trigger rule for table sizes. Alternatively, you could implement what CM currently does by scraping each tablet server's /metrics page and aggregating the data together per tablet/table.     [1] https://www.cloudera.com/documentation/enterprise/latest/topics/cm_dg_triggers_usecases.html ... 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

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

Thank you! It's really because storm workers are suffering GC pauses! We will check the code of storm workers. ... View more