[IMPALA-8984] Submit several same kudu table created query concurrently may result in table deleted in Kudu storage

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Impala 3.3.0
• Fix Version/s: Impala 3.4.0
• Component/s: Frontend
• Epic Color: ghx-label-1
• Assignee: Sheng Wang
• Reporter: Sheng Wang
• Created: 29/Sep/19 14:20
• Updated: 20/May/21 17:53
• Resolved: 13/Jan/20 09:05

Description

If the below query submitted several times concurrently, the result could be: All these queries finished, and table created in HMS, but not exists  in kudu storage. I've already found the reason, and I will submit the patch later.

create table if not exists test_kudu_table(
  logDay string,
  id int,
  primary key(logDay,id)
)
PARTITION BY RANGE (logDay)
(PARTITION VALUE = '2019-09-20')
STORED AS KUDU TBLPROPERTIES ('kudu.master_addresses'='master1:7051,master2:7051,master3:7051');

Issue Links

• is related to: IMPALA-9289 TestConcurrentKuduCreate is flaky
• relates to: IMPALA-10710 Log When Kudu Table Already Exists in HMS