[
https://issues.apache.org/jira/browse/HADOOP-11620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14330453#comment-14330453
]
Larry McCay commented on HADOOP-11620:
--------------------------------------
Thanks for the description of your intentions, [~asuresh].
I'm not sure that I see the value of having a single provider as greater than
the limitation of the loadbalancing of the KMS servers to having to all run on
the same port. As you said, it doesn't disable any existing functionality so
that is good.
Another question, why is it that we often put the burden of the loadbalancing
on the clients in Hadoop rather than put the servers behind a loadbalancing
process or VIP?
This pattern is common but is one that also makes it difficult to provide
elastic provisioning of server instances since all the clients config would
need to be made aware of the changes.
> Add Support for Load Balancing across a group of KMS servers for HA
> -------------------------------------------------------------------
>
> Key: HADOOP-11620
> URL: https://issues.apache.org/jira/browse/HADOOP-11620
> Project: Hadoop Common
> Issue Type: Improvement
> Components: kms
> Affects Versions: 2.6.0
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Attachments: HADOOP-11620.1.patch, HADOOP-11620.2.patch
>
>
> This patch needs to add support for :
> * specification of multiple hostnames in the kms key provider uri
> * KMS client to load balance requests across the hosts specified in the kms
> keyprovider uri.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
