By default, only 60 tablets (partitions) can be created at table creation time.  See the following limitation: https://kudu.apache.org/docs/known_issues.html#_scale But you can add any number of tablets later on by adding range partitions once a table is created. (hash partitions will not be allowed to add after table creation)   so you can not create 120 partition during table creation, but since you need hash partition, so I suggest you create 20 range partition multipled with 3 hash partition (need to use primary key columns for hash partition), so in this way, you create a 60 tablets table,  then after table creation, you can add more range partition by using "alter table" command from impala.   For the question about the number of hash partitions for a kudu table, there is no such formula, the purpose of hash parittion is just try to distribute rows by hash value and spread writes randomly among tablets, which helps mitigate hot-spotting and uneven tablet sizes. ... View more

apparently,  you have mismatch UUIDs for the 'master3.com'  peers { permanent_uuid: "8be74245ecaf4b5baf18b24dbc730922" member_type: VOTER last_known_addr { host: "master3.com" port: 7051 } }   as I can not see this UUID in consensus matrix  A = 865af50ae13e4cfagh5719b865d6716a B = c8d59ba15dbb4578900f597bb48bd9e0 C = 8be74245ecaf4b5baf18b24dbc7318ea   so what you can do now is to manually modify the consensus metadata on this 'B' host, so you need to stop this Kudu master role on 'B' host, then locate the directory - 'consensus-meta' on this  host (this folder could be either under the directory of 'fs_wal_dir' , or the first disk of 'fs_data_dirs'),  then you will use "kudu pbc dump 00000000000000000000000000000000" to check the all peers UUID, and I believe you will see the same wrong UUID - '8be74245ecaf4b5baf18b24dbc730922' in the output.   The actions you can take is to backup this 00000000000000000000000000000000 file, and use 'kudu pbc edit 00000000000000000000000000000000' to change the wrong UUID to '8be74245ecaf4b5baf18b24dbc7318ea' (the data displayed in "kudu pbc edit' is encoded UUID string, so you may want to check other 2 Master hosts to get the encoded UUID string.   after above, then you restart this master to see if this issue can be fixed.         ... View more

From the error you provided, it looks more like you have ingested data (from oracle) of type string, but want to insert it into a column defined as a varchar. It's not that kudu doesn't accept varchar types,  it's that the data itself is not a varchar type     ... View more