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 (Updated) (JIRA)" <ji...@apache.org> on 2011/12/19 22:57:30 UTC
[jira] [Updated] (TS-1050) Cached objects become inaccessible when
new volumes are added to the cache.
[ https://issues.apache.org/jira/browse/TS-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-1050:
------------------------------
Fix Version/s: 3.3.0
> Cached objects become inaccessible when new volumes are added to the cache.
> ---------------------------------------------------------------------------
>
> Key: TS-1050
> URL: https://issues.apache.org/jira/browse/TS-1050
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache
> Affects Versions: 3.1.1
> Reporter: B Wyatt
> Fix For: 3.3.0
>
>
> During the investigation of TS-949 it came to light that even a consistent hashing solution fails to maintain access for all objects in the cache when a new volume is added. This is because a new volume will necessarily assume ownership for some portion of the object/hash space. As a side effect of this ownership change, new searches for previously cached objects may return the new owner instead of the previous owner (which retained the cached copy). According to the volume itself (and thus several aggregate statistics like cache space usage), the objects are still valid and will remain as effective dead weight until evicted during the normal cache operation.
> See comments on TS-949 for initial discussion of possible solutions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira