Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-4952

Differentiate between resolved and unresolved IP addresses

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: Impala 2.9.0
    • Fix Version/s: None
    • Component/s: Distributed Exec
    • Labels:

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                henryr Henry Robinson
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: