Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-5305 Add https support in HDFS
  3. HDFS-5316

Namenode ignores the default https port

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 2.0.0-alpha
    • 2.3.0
    • None
    • None

    Description

      When dfs.https.enable is true and dfs.https.port is not configured, namenode does not pickup the default https port (50470), instead picks up random port. See:

      boolean needClientAuth = conf.getBoolean("dfs.https.need.client.auth", false);
            InetSocketAddress secInfoSocAddr = NetUtils.createSocketAddr(infoHost + ":" + conf.get(
              DFSConfigKeys.DFS_NAMENODE_HTTPS_PORT_KEY, "0"));
            Configuration sslConf = new Configuration(false);
            if (certSSL) {
              sslConf.addResource(conf.get(DFSConfigKeys.DFS_SERVER_HTTPS_KEYSTORE_RESOURCE_KEY,
                                           "ssl-server.xml"));
            }
      

      Unless https port is specifically configured as 0, we should not be picking random port. This needs to be documented in hdfs-default.xml

      Attachments

        1. HDFS-5316.000.patch
          3 kB
          Haohui Mai

        Activity

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

          People

            wheat9 Haohui Mai
            sureshms Suresh Srinivas
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment