Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: YARN-4757
    • Component/s: None
    • Labels:
      None

      Description

      In some environments, the entire container subnet may not be used exclusively by containers (ie the YARN nodemanager host IPs may also be part of the larger subnet).

      As a result, the reverse lookup zones created by the YARN Registry DNS server may not match those created on the forwarders.

      For example:

      Network: 172.27.0.0
      Subnet: 255.255.248.0

      Hosts:
      0.27.172.in-addr.arpa
      1.27.172.in-addr.arpa
      2.27.172.in-addr.arpa
      3.27.172.in-addr.arpa

      Containers
      4.27.172.in-addr.arpa
      5.27.172.in-addr.arpa
      6.27.172.in-addr.arpa
      7.27.172.in-addr.arpa

      YARN Registry DNS only allows for creating (as the total IP count is greater than 256):
      27.172.in-addr.arpa

      Provide configuration to further subdivide the subnets.

        Attachments

        1. YARN-5404-YARN-4757.004.patch
          17 kB
          Shane Kumpf
        2. YARN-5404-YARN-4757.003.patch
          17 kB
          Shane Kumpf
        3. YARN-5404-YARN-4757.002.patch
          16 kB
          Shane Kumpf
        4. YARN-5404-YARN-4757.001.patch
          16 kB
          Shane Kumpf
        5. YARN-5404-YARN-4757.001.patch
          16 kB
          Shane Kumpf
        6. YARN-5404-YARN-4757.001.patch
          16 kB
          Shane Kumpf
        7. YARN-5404.001.patch
          16 kB
          Shane Kumpf

          Activity

            People

            • Assignee:
              shanekumpf@gmail.com Shane Kumpf
              Reporter:
              shanekumpf@gmail.com Shane Kumpf
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved: