[
https://issues.apache.org/jira/browse/TS-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911434#comment-13911434
]
Zhao Yongming commented on TS-2184:
-----------------------------------
for the very HOT content in the cluster, we have another solution that tracking
of the hot content(in traffic view) and put them in the cluster_cache_local
list to make it dynamic. and this solution will need a workaround of the
purging, you need to broadcast all the purging to every machines in the cluster.
and pull from the hashing machine in the cluster is not implemented too. we are
testing to see how cool it will be. this function is provide by [~happy_fish100]
FYI
> Fetch from cluster with proxy.config.http.cache.cluster_cache_local enabled
> ---------------------------------------------------------------------------
>
> Key: TS-2184
> URL: https://issues.apache.org/jira/browse/TS-2184
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cache, Clustering
> Reporter: Scott Harris
> Assignee: Bin Chen
> Fix For: 6.0.0
>
>
> With proxy.config.http.cache.cluster_cache_local enabled I would like cluster
> nodes to store content locally but try to retrieve content from the cluster
> first (if not cached locally) and if no cluster nodes have content cached
> then retrieve from origin.
> Example - 2 Cluster nodes in Full cluster mode.
> 1. Node1 and Node2 are both empty.
> 2. Request to Node1 for "http://www.example.com/foo.html";.
> 3. Query Cluster for object
> 4. Not cached in cluster so retrieve from orgin, serve to client, object now
> cached on Node1.
> 5. Request comes to Node2 for "http://www.example.com/foo.html";.
> 6. Node2 retrieves cached version from Node1, serves to client, stores
> locally.
> 7. Subsequent request comes to Node1 or Node2 for
> "http://www.example.com/foo.html";, object is served to client from local
> cache.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
