[
https://issues.apache.org/jira/browse/KUDU-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17675642#comment-17675642
]
ASF subversion and git services commented on KUDU-3357:
-------------------------------------------------------
Commit cdc97be9aaecb3232f174786ad60d9e30d6a78dd in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=cdc97be9a ]
KUDU-3357 proxied RPCs for multi-master Kudu clusters
With this patch, it's now possible to run a multi-master Kudu cluster in
a local area network while processing RPC requests sent from external
networks. The RPC requests are assumed to be forwarded by a TCP proxy
which advertises RPC endpoints for the masters and the tablet servers
of the multi-master Kudu cluster.
Refactored and unified test scenarios in client-proxied-rpc-test provide
the coverage for the newly added functionality.
This is a follow-up to 3f29b5da5f59ea96cfec0608226d5c35740884a6.
Change-Id: Id834d5fae8dcc2230de9f6b6429334c24052011a
Reviewed-on: http://gerrit.cloudera.org:8080/19404
Reviewed-by: Attila Bukor <[email protected]>
Reviewed-by: Zoltan Chovan <[email protected]>
Tested-by: Alexey Serbin <[email protected]>
> Allow servers to not use the advertised RPC addresses
> -----------------------------------------------------
>
> Key: KUDU-3357
> URL: https://issues.apache.org/jira/browse/KUDU-3357
> Project: Kudu
> Issue Type: Improvement
> Components: rpc
> Reporter: Andrew Wong
> Assignee: Alexey Serbin
> Priority: Major
> Fix For: 1.17.0
>
>
> When Kudu servers are deployed within an internal network with internal
> hostnames (e.g. in a k8s cluster), and Kudu clients are deployed outside of
> this network with a mapping of external traffic to internal ports (e.g. with
> a load balancer), it’s unclear how to route the Kudu client to the servers
> without having all traffic (including RPCs between servers) use publicly
> accessible addresses.
> For instance, all servers could be configured with the
> --rpc_advertised_addreses configuration. However, since these addresses are
> used to register servers with the Master, not only would they be used to
> indicate where clients should look for data, but they would also be used to
> indicate where replicas should heartbeat to other replicas. This would induce
> a great deal of traffic on the load balancer.
> We should consider allowing “internal” (i.e. tserver and master) traffic to
> bypass advertised addresses and use an alternate address. Or at the very
> least, introduce a policy for selecting which advertised address to use
> depending on what is available (currently, we always the first in the list).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
