[IMPALA-4952] Differentiate between resolved and unresolved IP addresses

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: Impala 2.9.0
• Component/s: Distributed Exec
• Labels: scheduler
• Target Version: Impala 2.13.0
• Assignee: Unassigned
• Reporter: Henry Robinson
• Created: 18/Feb/17 00:42
• Updated: 21/Dec/20 19:06
• Resolved: 21/Dec/20 19:06

Description

KRPC (IMPALA-2567) requires resolved IP addresses. Since RPCs happen frequently, and IP resolution can be expensive, it makes sense to retain resolved addresses where possible.

The scheduler already knows the resolved address for every backend. However, the logic is very complex, and there's not really a good way to know at compile time whether or not we're using a resolved address or not.

We can address this by adding a new type - perhaps ResolvedAddress : public TNetworkAddress, and requiring that RpcMgr::GetProxy() etc take a ResolvedAddress. That way the compiler will complain if we don't prove to it that the address is resolved. We can make it hard to construct a ResolvedAddress without actually resolving some string into an IPV4 address.

Issue Links

• relates to: IMPALA-2567 KRPC milestone 1