Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-6760

WebServer shouldn't increase port number in case of negative port setting caused by Jetty's race

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.20.3
    • 0.20.3
    • None
    • None
    • Reviewed

    Description

      When a negative port is assigned to a webserver socket (because of a race inside of the Jetty server) the workaround from HADOOP-6386 is increasing the original port number on the next bind attempt. Apparently, this is an incorrect logic and next bind attempt should happen on the same port number if possible.

      Attachments

        1. HADOOP-6760.0.20.patch
          2 kB
          Konstantin I Boudnik
        2. HADOOP-6760.0.20.patch
          0.6 kB
          Konstantin I Boudnik
        3. HADOOP-6760.0.20.patch
          2 kB
          Konstantin I Boudnik
        4. HADOOP-6760.0.20.patch
          2 kB
          Konstantin I Boudnik
        5. HADOOP-6760.0.20.patch
          0.6 kB
          Konstantin I Boudnik
        6. HADOOP-6760.patch
          1 kB
          Konstantin I Boudnik
        7. HADOOP-6760.patch
          2 kB
          Konstantin I Boudnik
        8. HADOOP-6760.patch
          0.5 kB
          Konstantin I Boudnik

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. HADOOP-6386 NameNode's HttpServer can't instantiate InetSocketAddress: IllegalArgumentException is thrown

          • Blocker - Blocks development and/or testing work, production could not run
          • Closed

          Activity

            People

              cos Konstantin I Boudnik
              cos Konstantin I Boudnik
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: