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

HTTP SM holds the cache write lock for too long

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • 7.1.0
    • HTTP

    Description

      It seems we open the cache for write very early on in the HTTP SM, which can have very bad effect on performance if the object is not cacheable. It's not totally clear as to why this is done this way, but we should examine this for v3.1, and try to minimize how long we hold the lock. It's possible this is related to read_while_writer, but then it should be modified IMO.

      Attachments

        Issue Links

          Is contained by

          Improvement - An improvement or enhancement to an existing feature or task. TS-974 TS should have a mode to hold partial objects in cache

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

          Bug - A problem which impairs or prevents the functions of the product. TS-1463 rfc5861 plugin does not return stale data upon subsequent requests

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. TS-1996 Remove TSHttpTxnNewCacheLookupDo API

          • Major - Major loss of function.
          • Open

          Activity

            People

              amc Alan M. Carroll
              zwoop Leif Hedstrom
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: