[
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: (was: sometime)
4.2.0
Assignee: Alan M. Carroll
Alan: Please take a look at this bug, and decide what to do. Is this a dupe?
New feature? Something you are or will fix?
> 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
> Assignee: Alan M. Carroll
> Fix For: 4.2.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 was sent by Atlassian JIRA
(v6.1.5#6160)
