Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-11110

JavaKeystoreProvider should not report a key as created if it was not flushed to the backing file

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.0
    • Fix Version/s: 2.6.0
    • Component/s: None
    • Labels:
      None
    • Target Version/s:

      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.

        Attachments

        1. HADOOP-11110.2.patch
          14 kB
          Arun Suresh
        2. HADOOP-11110.1.patch
          11 kB
          Arun Suresh

          Activity

            People

            • Assignee:
              asuresh Arun Suresh
              Reporter:
              andrew.wang Andrew Wang
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: