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

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.20.3
    • Fix Version/s: 0.20.3
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      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.patch
          0.5 kB
          Konstantin Boudnik
        2. HADOOP-6760.patch
          2 kB
          Konstantin Boudnik
        3. HADOOP-6760.patch
          1 kB
          Konstantin Boudnik
        4. HADOOP-6760.0.20.patch
          0.6 kB
          Konstantin Boudnik
        5. HADOOP-6760.0.20.patch
          2 kB
          Konstantin Boudnik
        6. HADOOP-6760.0.20.patch
          2 kB
          Konstantin Boudnik
        7. HADOOP-6760.0.20.patch
          0.6 kB
          Konstantin Boudnik
        8. HADOOP-6760.0.20.patch
          2 kB
          Konstantin Boudnik

          Issue Links

            Activity

              People

              • Assignee:
                cos Konstantin Boudnik
                Reporter:
                cos Konstantin Boudnik
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: