hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-11110) JavaKeystoreProvider should not report a key as created if it was not flushed to the backing file
Date Mon, 29 Sep 2014 20:11:35 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-11110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Wang updated HADOOP-11110:
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.6.0
           Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2, thanks Arun.

> JavaKeystoreProvider should not report a key as created if it was not flushed to the
backing file
> -------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-11110
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11110
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Andrew Wang
>            Assignee: Arun Suresh
>             Fix For: 2.6.0
>
>         Attachments: HADOOP-11110.1.patch, HADOOP-11110.2.patch
>
>
> Testing with the KMS backed by JKS reveals the following:
> {noformat}
> [root@dlo-4 ~]# hadoop key create testkey -provider kms://http@localhost:16000/kms
> testkey has not been created. Mkdirs failed to create file:xxxxx
> ....<stack trace>....
> [root@dlo-4 ~]# hadoop key list -provider kms://http@localhost:16000/kms
> Listing keys for KeyProvider: KMSClientProvider[http://localhost:16000/kms/v1/]
> testkey
> {noformat}
> The JKS still has the key in memory and serves it up, but will disappear if the KMS is
restarted since it's not flushed to the file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message