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

Change default NameNode RPC port back to 8020

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

    • Task
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 3.0.0
    • 3.0.1
    • namenode
    • None
    • Incompatible change, Reviewed
    • Hide
      HDFS NameNode default RPC port is changed back to 8020. The only official release that has this differently is 3.0.0, which used 9820.

      It is recommended for 2.x users to upgrade to 3.0.1+, to reduce the burden on changing default NN RPC port.
      Show
      HDFS NameNode default RPC port is changed back to 8020. The only official release that has this differently is 3.0.0, which used 9820. It is recommended for 2.x users to upgrade to 3.0.1+, to reduce the burden on changing default NN RPC port.

    Description

      In HDFS-9427 (HDFS should not default to ephemeral ports), we changed all default ports to ephemeral ports, which is very appreciated by admin. As part of that change, we also modified the NN RPC port from the famous 8020 to 9820, to be closer to other ports changed there.

      With more integration going on, it appears that all the other ephemeral port changes are fine, but the NN RPC port change is painful for downstream on migrating to Hadoop 3. Some examples include:

      1. Hive table locations pointing to hdfs://nn:port/dir
      2. Downstream minicluster unit tests that assumed 8020
      3. Oozie workflows / downstream scripts that used 8020

      This isn't a problem for HA URLs, since that does not include the port number. But considering the downstream impact, instead of requiring all of them change their stuff, it would be a way better experience to leave the NN port unchanged. This will benefit Hadoop 3 adoption and ease unnecessary upgrade burdens.

      It is of course incompatible, but giving 3.0.0 is just out, IMO it worths to switch the port back.

      Attachments

        Issue Links

        Activity

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

          People

            xiaochen Xiao Chen Assign to me
            xiaochen Xiao Chen
            Votes:
            0 Vote for this issue
            Watchers:
            23 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment