You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2015/07/01 01:56:06 UTC

[jira] [Created] (TS-3729) cache_promote: Can crash / assert under conditions where origin is very slow

Leif Hedstrom created TS-3729:
---------------------------------

             Summary: cache_promote: Can crash / assert under conditions where origin is very slow
                 Key: TS-3729
                 URL: https://issues.apache.org/jira/browse/TS-3729
             Project: Traffic Server
          Issue Type: Bug
          Components: Plugins
            Reporter: Leif Hedstrom


If the response from origin is very slow (> 60s), until ATS gets the headers, there's a window where cache_promote can assert and crash. This is a similar problem to other places where we ended up having to ref-count the continuation and remap configuration.

Since we defer the cache control until "read-response-header" due to TS-3426, this is an unfortunate (and temporary) problem. At the point where this hook needs to execute, we don't need access to the remap data or continuation, so my solution / proposal is that we just use a global continuation that is unrelated to the remap configs, and schedule it when this deferred cache control is needed. Later, we can then remove it completely.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)