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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.0
• Fix Version/s: 2.6.0
• Target Version/s: 2.6.0
• Assignee: Arun Suresh
• Reporter: Andrew Wang
• Created: 19/Sep/14 01:40
• Updated: 01/Dec/14 03:11
• Resolved: 29/Sep/14 20:10

Description

Testing with the KMS backed by JKS reveals the following:

[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

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.