I think those messages are harmless and indicative of an underlying issue
of leader elections, perhaps caused by load. The full ksck output would be
helpful to understand more.
This shouldn't cause writes to be lost. More likely the data was not
written at all- are you checking for the success of
Hi:
I used CDH5.14.0,kudu version is 1.6.0 (3 kudu master,7 kudu ts), Kudu ts
and yarn mix and deploy on the same machine. 8 SAS on each TS machine (1T
capacity)
When I query the kudu table with impala, the kudu tsserver appears
unavailable. The tsserver log:
Log line format: [IWEF]mmdd
