You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Phil Sorber (JIRA)" <ji...@apache.org> on 2012/09/13 04:31:07 UTC
[jira] [Created] (TS-1463) rfc5861 plugin does not return stale
data upon subsequent requests
Phil Sorber created TS-1463:
-------------------------------
Summary: rfc5861 plugin does not return stale data upon subsequent requests
Key: TS-1463
URL: https://issues.apache.org/jira/browse/TS-1463
Project: Traffic Server
Issue Type: Bug
Reporter: Phil Sorber
Assignee: Phil Sorber
Upon subsequent requests the cache returns MISS instead of STALE so the plugin isn't able to return the stale response properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1463) rfc5861 plugin does not return stale
data upon subsequent requests
Posted by "Kit Chan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454699#comment-13454699 ]
Kit Chan commented on TS-1463:
------------------------------
So the base problem is that once the async call established a connection with the origin server and is ready to receive data from it, the stale copy/resource is no longer available and subsequent requests will result in a TCP_MISS and an extra call to the origin server
So here are some of my thoughts/options. Not very well organized and are open for discussions
1) I think it is highly unlikely. It seems each cache key can have only one value. So if each cache key can have 2 value, then we can keep one for stale copy while the one is active fresh. But then of course memory consumption will increase.
2) If the url is "http://www.example.com/", the async call can be made for "http://www.example.com/?_swr=1". This will result in the async call using a separate cache key. Once the async call is done, we need another way to change the value of the original cache key. (We can change the value of original cache key by POSTing the result to the original cache key url and use TSHttpTxnIntercept() to intercept this request and stop it from reaching origin server. The intercept code will then return with a normal cacheable response and result in changing the value of the cache key. Is there a simpler way than this?)
> rfc5861 plugin does not return stale data upon subsequent requests
> ------------------------------------------------------------------
>
> Key: TS-1463
> URL: https://issues.apache.org/jira/browse/TS-1463
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Phil Sorber
> Assignee: Phil Sorber
>
> Upon subsequent requests the cache returns MISS instead of STALE so the plugin isn't able to return the stale response properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1463) rfc5861 plugin does not return stale
data upon subsequent requests
Posted by "Phil Sorber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475973#comment-13475973 ]
Phil Sorber commented on TS-1463:
---------------------------------
I'm sorry, I have been busy lately and unable to look into this. It is still at the top of my "when I have free time" list though.
> rfc5861 plugin does not return stale data upon subsequent requests
> ------------------------------------------------------------------
>
> Key: TS-1463
> URL: https://issues.apache.org/jira/browse/TS-1463
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Phil Sorber
> Assignee: Phil Sorber
> Fix For: 3.3.2
>
>
> Upon subsequent requests the cache returns MISS instead of STALE so the plugin isn't able to return the stale response properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-1463) rfc5861 plugin does not return stale
data upon subsequent requests
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-1463:
------------------------------
Fix Version/s: 3.3.2
> rfc5861 plugin does not return stale data upon subsequent requests
> ------------------------------------------------------------------
>
> Key: TS-1463
> URL: https://issues.apache.org/jira/browse/TS-1463
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Phil Sorber
> Assignee: Phil Sorber
> Fix For: 3.3.2
>
>
> Upon subsequent requests the cache returns MISS instead of STALE so the plugin isn't able to return the stale response properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1463) rfc5861 plugin does not return stale
data upon subsequent requests
Posted by "Phil Sorber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13480451#comment-13480451 ]
Phil Sorber commented on TS-1463:
---------------------------------
Ok, I have confirmed this problem. It seems that the cache locks the key before it goes to get the new content (which makes sense), but that prohibits me from getting the stale content while it is waiting and not writing.
Still thinking about the best way to resolve this.
> rfc5861 plugin does not return stale data upon subsequent requests
> ------------------------------------------------------------------
>
> Key: TS-1463
> URL: https://issues.apache.org/jira/browse/TS-1463
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Phil Sorber
> Assignee: Phil Sorber
> Fix For: 3.3.2
>
>
> Upon subsequent requests the cache returns MISS instead of STALE so the plugin isn't able to return the stale response properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1463) rfc5861 plugin does not return stale
data upon subsequent requests
Posted by "Kit Chan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473590#comment-13473590 ]
Kit Chan commented on TS-1463:
------------------------------
Phil, you have any updates/comments?
> rfc5861 plugin does not return stale data upon subsequent requests
> ------------------------------------------------------------------
>
> Key: TS-1463
> URL: https://issues.apache.org/jira/browse/TS-1463
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Phil Sorber
> Assignee: Phil Sorber
> Fix For: 3.3.2
>
>
> Upon subsequent requests the cache returns MISS instead of STALE so the plugin isn't able to return the stale response properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira