hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rushabh S Shah (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-14563) LoadBalancingKMSClientProvider#warmUpEncryptedKeys swallows IOException
Date Wed, 21 Jun 2017 14:18:00 GMT
Rushabh S Shah created HADOOP-14563:

             Summary: LoadBalancingKMSClientProvider#warmUpEncryptedKeys swallows IOException
                 Key: HADOOP-14563
                 URL: https://issues.apache.org/jira/browse/HADOOP-14563
             Project: Hadoop Common
          Issue Type: Bug
    Affects Versions: 2.8.1
            Reporter: Rushabh S Shah
            Assignee: Rushabh S Shah

TestAclsEndToEnd is failing consistently in HADOOP-14521.
The reason behind it is LoadBalancingKMSClientProvider#warmUpEncryptedKeys swallows IOException
while KMSClientProvider#warmUpEncryptedKeys throws all the way back to createEncryptionZone
and creation of EZ fails.
Following are the relevant piece of code snippets.
  public void warmUpEncryptedKeys(String... keyNames)
      throws IOException {
    try {
    } catch (ExecutionException e) {
      throw new IOException(e);

   // This request is sent to all providers in the load-balancing group
  public void warmUpEncryptedKeys(String... keyNames) throws IOException {
    for (KMSClientProvider provider : providers) {
      try {
      } catch (IOException ioe) {
            "Error warming up keys for provider with url"
            + "[" + provider.getKMSUrl() + "]", ioe);
In HADOOP-14521, I intend to always instantiate LoadBalancingKMSClientProvider even if there
is only one provider so that the retries can applied at only one place.
We need to decide whether we want to fail in both the case or continue.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org

View raw message