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

Client should always ask namenode for kms provider path.

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.9.0, 3.0.0-alpha4, 2.8.2
    • kms
    • None

    Description

      According to current implementation of kms provider in client conf, there can only be one kms.
      In multi-cluster environment, if a client is reading encrypted data from multiple clusters it will only get kms token for local cluster.
      Not sure whether the target version is correct or not.

      Attachments

        1. HADOOP-14104-trunk-v5.patch
          38 kB
          Rushabh Shah
        2. HADOOP-14104-trunk-v4.patch
          38 kB
          Rushabh Shah
        3. HADOOP-14104-trunk-v3.patch
          38 kB
          Rushabh Shah
        4. HADOOP-14104-trunk-v2.patch
          39 kB
          Rushabh Shah
        5. HADOOP-14104-trunk-v1.patch
          30 kB
          Rushabh Shah
        6. HADOOP-14104-trunk.patch
          28 kB
          Rushabh Shah
        7. HADOOP-14104-branch-2.patch
          38 kB
          Rushabh Shah
        8. HADOOP-14104-branch-2.8.patch
          38 kB
          Rushabh Shah

        Issue Links

        breaks

        Bug - A problem which impairs or prevents the functions of the product. HDFS-13696 Distcp between 2 secure clusters and non encrypted zones fails with connection timeout

        • Critical - Crashes, loss of data, severe memory leak.
        • Open

        Bug - A problem which impairs or prevents the functions of the product. HADOOP-14814 Fix incompatible API change on FsServerDefaults to HADOOP-14104

        • Blocker - Blocks development and/or testing work, production could not run
        • Resolved

        Bug - A problem which impairs or prevents the functions of the product. HDFS-11689 New exception thrown by DFSClient#isHDFSEncryptionEnabled broke hacky hive code

        • Major - Major loss of function.
        • Resolved

        Bug - A problem which impairs or prevents the functions of the product. HDFS-11702 Remove indefinite caching of key provider uri in DFSClient

        • Major - Major loss of function.
        • Resolved
        is related to

        Improvement - An improvement or enhancement to an existing feature or task. HDFS-11687 Add new public encryption APIs required by Hive

        • Major - Major loss of function.
        • Resolved

        Improvement - An improvement or enhancement to an existing feature or task. HIVE-16490 Hive should not use private HDFS APIs for encryption

        • Critical - Crashes, loss of data, severe memory leak.
        • Closed
        relates to

        Bug - A problem which impairs or prevents the functions of the product. HDFS-13371 NPE for FsServerDefaults.getKeyProviderUri() for clientProtocol communication between 2.7 and 3.X

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Resolved

        Improvement - An improvement or enhancement to an existing feature or task. HADOOP-16350 Ability to tell HDFS client not to request KMS Information from NameNode

        • Major - Major loss of function.
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            shahrs87 Rushabh Shah Assign to me
            shahrs87 Rushabh Shah
            Votes:
            0 Vote for this issue
            Watchers:
            18 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment