[ https://issues.apache.org/jira/browse/TS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhao Yongming resolved TS-32. ----------------------------- Resolution: Fixed I am closing this issue, credits to [~g-adachi], many thanks please open new issues for the other ICP bugs. although ICP is working now, the local network cache clustering should consider Cluster. > Fix ICP > ------- > > Key: TS-32 > URL: https://issues.apache.org/jira/browse/TS-32 > Project: Traffic Server > Issue Type: Bug > Components: Core > Affects Versions: 3.0.0 > Reporter: Miles Libbey > Assignee: Zhao Yongming > Fix For: 4.2.0 > > Attachments: TS-32-icp-basic-3.2.x.diff, TS-32-icp-basic-master.diff, > TS-32-icp-multicast-3.2.x.diff, TS-32-icp-multicast-master.diff, > TS-32-segfault-workaround.diff > > > {color:red} > ICP is broken in all the releases and master, but we have options for that: > inter-colo peering to use the parent.config, local network peering to use the > cluster. > refer to the official docutments for parent.config and cluster howto. > {color} > http://icp.ircache.net/ > The ICP implementation in Traffic Server broke when epoll() was introduced. > Its still an interesting and used feature in caches: > - when a caching layer of several boxes are used ICP helps to reduce > disparities when a client is not routed to the same cache on subsequent > requests > - after a restart, it can help reduce the time spent in a cold cache situation -- This message was sent by Atlassian JIRA (v6.1.5#6160)