[IMPALA-8339] Coordinator should be more resilient to fragment instances startup failure - ASF JIRA

Attach files

Attach Screenshot

Voters

Watch issue

Watchers

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Sub-task
Status: Resolved
Priority: Critical
Resolution: Fixed
Affects Version/s: None
Fix Version/s: Impala 3.3.0
Component/s: Distributed Exec
Labels:
- Availability
- resilience

Epic Color:
ghx-label-7

Description

Impala currently relies on statestore for cluster membership. When an Impala executor goes offline, it may take a while for statestore to declare that node as unavailable and for that information to be propagated to all coordinator nodes. Within this window, some coordinator nodes may still attempt to issue RPCs to the faulty node, resulting in RPC failures which resulted in query failures. In other words, many queries may fail to start within this window until all coordinator nodes get the latest information on cluster membership.

Going forward, coordinator may need to fall back to using backup executors for each fragments in case some of the executors are not available. Moreover, coordinator should treat the cluster membership information from statestore (or any external source of truth e.g. etcd) as hints instead of ground truth and adjust the scheduling of fragment instances based on the availability of the executors from the coordinator's perspective.