Juanes Palma Bueno created IMPALA-11221:
-------------------------------------------
Summary: Impala loses to trace Kudu leader balance
Key: IMPALA-11221
URL: https://issues.apache.org/jira/browse/IMPALA-11221
Project: IMPALA
Issue Type: Bug
Components: Catalog
Affects Versions: Impala 3.4.0
Environment: Red Hat Enterprise Linux Server 7.8
CDP 7.1.6
CM 7.1.3
Reporter: Juanes Palma Bueno
Attachments: cdp_env.png
In an HA cluster with 3 Kudu Master servers, (see attachment)
when the server where Kudu leader goes down (Master2) all queries against kudu
become unavailable.
Query: select * from foo_table limit 3
Query submitted at: 2022-04-04 08:38:32 (Coordinator:
http://worker2.server.com:25000)
{color:#de350b}ERROR: ImpalaRuntimeException: Unable to initialize the Kudu
scan node{color}
CAUSED BY: AnalysisException: Unable to open the Kudu table: schema.foo_table
CAUSED BY: NonRecoverableException: cannot complete before timeout:
KuduRpc(method=GetTableSchema, tablet=Kudu Master, attempt=1,
TimeoutTracker(timeout=180000, elapsed=180004), Trace Summary(0 ms): Sent(1),
Received(0), Delayed(0), MasterRefresh(0), AuthRefresh(0), Truncated: false
Sent: (master2:7051, [ GetTableSchema, 1 ]))
The coordinator it's trying to get the metadata information from the Kudu
Master that is already down (master2), meanwhile there are still 2 Kudu Masters
UP and one of them was already elected as Leader:
uuid | rpc-addresses | role
----------------------------------+---------------------------------+----------
daa9129e78244be2aaa7e5e649cc1dc8 | master1:7051 | FOLLOWER
1f02c618009c44d381c55841dcb5a498 | master3:7051 | LEADER
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
