You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Arun Suresh (JIRA)" <ji...@apache.org> on 2014/09/21 13:27:34 UTC

[jira] [Updated] (HADOOP-11110) JavaKeystoreProvider should not report a key as created if it was not flushed to the backing file

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

Arun Suresh updated HADOOP-11110:
---------------------------------
    Status: Patch Available  (was: Open)

> 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
>         Attachments: HADOOP-11110.1.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)