[
https://issues.apache.org/jira/browse/IMPALA-8659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-8659.
-----------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> Allow self-RPCs for KRPC to go via loopback
> -------------------------------------------
>
> Key: IMPALA-8659
> URL: https://issues.apache.org/jira/browse/IMPALA-8659
> Project: IMPALA
> Issue Type: Improvement
> Components: Distributed Exec
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Fix For: Impala 3.3.0
>
>
> Our KRPC implementation currently sends all RPCs, even those to the current
> host, through a single external IP. There are some cases why we might not
> want to do this. The immediately motivating issue for me is bugs in some
> tooling that cause self-RPCs on external IPs to fail. See
> https://github.com/istio/istio/issues/12551.
> There are really two parts to this:
> * Listening on the 127.0.0.1 interface
> * Intercepting RPCs to the external IP and sending them to 127.0.0.1 instead.
> An alternative solution would be to completely bypass the RPC stack, but that
> would be far more invasive.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
