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

Addendum for HDFS-9579: to handle the case when client machine can't resolve network path

VotersStop watchingWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.9.0, 3.0.0-alpha1
    • None
    • None
    • Reviewed

    Description

      If DFSClient runs on a machine that can't resolve network path, DNSToSwitchMapping will return DEFAULT_RACK. In addition, if somehow dnsToSwitchMapping.resolve returns null, that will cause exception when it tries to create clientNode. In either case, there is no need to create clientNode and we should treat its network distance with any datanode as Integer.MAX_VALUE.

          clientNode = new NodeBase(clientHostName,
              dnsToSwitchMapping.resolve(nodes).get(0));
      

      Attachments

        1. HDFS-10208.patch
          7 kB
          Ming Ma
        2. HDFS-10208-2.patch
          14 kB
          Ming Ma
        3. HDFS-10208-3.patch
          18 kB
          Ming Ma
        4. HDFS-10208-4.patch
          19 kB
          Ming Ma
        5. HDFS-10208-5.patch
          19 kB
          Ming Ma

        Issue Links

        Activity

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

          People

            mingma Ming Ma
            mingma Ming Ma
            Votes:
            0 Vote for this issue
            Watchers:
            6 Stop watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment