Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-2950

Secondary NN HTTPS address should be listed as a NAMESERVICE_SPECIFIC_KEY

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

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 0.23.0
    • 0.23.2
    • namenode
    • None
    • Reviewed
    • The configuration dfs.secondary.https.port has been renamed to dfs.namenode.secondary.https-port for consistency. The old configuration is still supported via a deprecation path.

    Description

      This config was mistakenly left out of the NAMESERVICE_SPECIFIC_KEY map, which makes it tougher to configure federated clusters with security.

      Attachments

        Issue Links

        is related to

        Sub-task - The sub-task of the issue HDFS-2935 HA: Shared edits dir property should be suffixed with nameservice and namenodeID

        • Major - Major loss of function.
        • Resolved

        Improvement - An improvement or enhancement to an existing feature or task. MAPREDUCE-3864 Fix cluster setup docs for correct SNN HTTPS parameters

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

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

          People

            tlipcon Todd Lipcon Assign to me
            tlipcon Todd Lipcon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment