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

Updated maxIdleTime default in the code to match core-default.xml

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Trivial
    • Resolution: Fixed
    • 1.0.0, 0.21.0, 0.22.0, 0.23.0
    • 0.23.1
    • ipc
    • None
    • Reviewed

    Description

      HADOOP-2909 intended to set the server max idle time for a connection to twice the client value. ("The server-side max idle time should be greater than the client-side max idle time, for example, twice of the client-side max idle time.") This way when a server times out a connection it's due a crashed client and not an inactive client so we don't close client connections with outstanding requests (by setting 2x the client value on the server side the client should time out the connection first).

      Looks like there was a typo in the patch and it set the default value to 1/5th the client value, instead of the intended 2x.

      hadoop2 (pre-HADOOP-4687)$ git reset --hard 6fa4597e
      hadoop2 (pre-HADOOP-4687)$ grep -r ipc.client.connection.maxidletime . 
      ./src/core/org/apache/hadoop/ipc/Client.java:      conf.getInt("ipc.client.connection.maxidletime", 10000); //10s
      ./src/core/org/apache/hadoop/ipc/Server.java:    this.maxIdleTime = 2*conf.getInt("ipc.client.connection.maxidletime", 1000);
      

      Attachments

        1. hadoop-7949.txt
          11 kB
          Eli Collins
        2. hadoop-7949.txt
          11 kB
          Eli Collins

        Issue Links

        Activity

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

          People

            eli Eli Collins
            eli Eli Collins
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment