[ 
https://issues.apache.org/jira/browse/IMPALA-8659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863156#comment-16863156
 ] 

ASF subversion and git services commented on IMPALA-8659:
---------------------------------------------------------

Commit 8ee18c3b7736e02ef76507162ed2592ba11d16e3 in impala's branch 
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=8ee18c3 ]

IMPALA-8659: Allow self-RPCs for KRPC to go via loopback

Adds a flag --rpc_use_loopback that causes two differences
in behaviour when enabled:
1. KRPC will listen on all interfaces, i.e. bind the socket
   to INADDR_ANY.
2. KRPC RPCs to --hostname are sent to 127.0.0.1 instead of
   the IP (maybe external) that --hostname resolves to.

There is no change in default behaviour, except in containers,
where this flag is enabled by default.

Testing:
* Added a custom cluster test, which runs in exhaustive,
  as a sanity test for the behaviour of the flag.

Change-Id: I9dbd477769ed49c05e624f06da4e51afaaf1670d
Reviewed-on: http://gerrit.cloudera.org:8080/13592
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> 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
>
> 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]

Reply via email to