Uploaded image for project: 'Traffic Server'
  1. Traffic Server
  2. TS-608

Is HttpSessionManager::purge_keepalives() too aggressive?

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • None
    • HTTP
    • None

    Description

      It seems that if we trigger the "max server connections", we call this purge function in the session manager, which will close all currently open keep-alive connections. This seems very aggressive, why not limit it to say only removing 10% of each "bucket" or some such? Also, how does this work together with per-origin limits? Ideally, if the per-origin limits are in place, we would only purge sessions that are for the IP we wish to connect to ?

      Attachments

        1. TS-608.patch
          3 kB
          mohan_zl

        Issue Links

          is superceded by

          New Feature - A new feature of the product, which has yet to be developed. TS-3313 New World order for connection management and timeouts

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. TS-2863 FQDN session pools work poorly

          • Major - Major loss of function.
          • Closed

          Activity

            People

              bcall Bryan Call
              zwoop Leif Hedstrom
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: