Hi everyone,   We use CDH to manage our data using Kudu and Impala. Whenever we restart Kudu, we see very high start up times to the tune of an hour or more. When we run ksck during this time we get the following (summary at the end):   ================== Errors: ================== table consistency check error: Corruption: 51 out of 74 table(s) are bad FAILED Runtime error: ksck discovered errors All the other tables are either under replicated or unavailable. Is this normal? Any help in making this faster will be appreciated.   Thanks, -- Razee ... View more