As you specified the 'kudu.master_addresse' property in the CREATE TABLE statements, Impala requires ALL privileges on SERVER. That error message also indicated that: ERROR: AuthorizationException: User 'yydp/bigdata5@TEST.COM' does not have privileges to access: server1. So you may want to either remove that clause (and set the Kudu master address via-kudu_master_hosts flag), or grant ALL on SERVER to that user. ... View more

Hi, I am facing the same issue in my cluster. The trusted subnet flag is not configured with any value in my cluster. I have 3 masters. Please guide me what values to set in the trusted subnet flag. ... View more

Another thing worth mentioning about Impala bulk inserts into Kudu: you may benefit from the /* +noshuffle,noclustered */ insert hint, or from setting a MEM_LIMIT, as outlined here: https://www.cloudera.com/documentation/enterprise/6/6.2/topics/impala_hints.html ... View more

You don't need to take down the other masters, but need to establish a maintenance window (no DDLs) to ensure the table metadata is consistent between followers and the leader. If it is hard in production, alternative is to ensure the master to be taken down is not the leader (to avoid lose data). ... View more

Hi Rahul,   The error you encountered "Service unavailable: Error reading clock. Clock considered unsynchronized" means either the NTP is not installed, or if the clock is reported as unsynchronized, see NTP Clock Synchronization for trouble shooting. Best, Hao ... View more

yes if some table have many operation (insert / update) in 24 hours, the query performance go down significantly mrs is not col-storage i guess ... View more

Sounds like good news. Thanks for the update! ... View more

You're welcome. If that worked for you, please mark my response as the answer / solution to your question. ... View more

Hi @Pettax Thanks, your solution work with me too. ... View more