Major Description
Running ksck against a cluster with 3 tables each having three tablets while restricting ksck to just check one tablet shows the following wrong summary table:
$ build/latest/bin/kudu cluster ksck 127.0.0.1:9878,127.0.0.1:9877,127.0.0.1:9876 -tablets=2d14df764be34f948ef225cc49e5e37f
Connected to the Master
Fetched info from all 5 Tablet Servers
Table loadgen_auto_95d5198227bd4b93ba412cef94005397 is HEALTHY (0 tablet(s) checked)
Table loadgen_auto_c159d0d2aec140bda8b735a3603f50dd is HEALTHY (0 tablet(s) checked)
Table loadgen_auto_1cdce4a07ae546abb0d757d804d66e0e is HEALTHY (1 tablet(s) checked)
Table Summary
Name | Status | Total Tablets | Healthy | Under-replicated | Unavailable
-----------------------------------------------+---------+---------------+---------+------------------+-------------
loadgen_auto_1cdce4a07ae546abb0d757d804d66e0e | HEALTHY | 1 | 1 | 0 | 0
loadgen_auto_95d5198227bd4b93ba412cef94005397 | HEALTHY | 0 | 0 | 0 | 0
loadgen_auto_c159d0d2aec140bda8b735a3603f50dd | HEALTHY | 0 | 0 | 0 | 0
The metadata for 3 table(s) is HEALTHY
OK
This is pretty misleading, and a lot of worthless output besides.