Hello, On 04/02/2014 16:09, Alan M. Carroll wrote: > Tuesday, February 4, 2014, 1:39:37 AM, you wrote: > >> Hello, >> I configured TrafficServer, in virtual machines, to use raw disks as >> cache. Currently 2 disks of 10G each. >> TrafficServer now reports 80% of cache used. > >> Basically, I see 2 solutions: >> - Add more disk space (best one because Trafficservers are behind a >> Load-balancer) >> - Add more servers (which won't solve the per server disk usage) > > I would recommend taking the third option, just let it run. It is completely > normal and expected for the Traffic Server cache to become full. All of the > deployments I know of treat this as the normal state. Traffic Server will > evict old content from the cache as needed.
Problem is, TrafficServer is used to cache API calls. And API usage is limited by daily quota, so I definitely need to add more capacity :) >> Regarding first solution, I wonder how raw disk cache exactly works, in >> terms of repartition ? > >> Adding new disk, will trafficserver: >> - invalidate part of the cache (sort of sharding) ? >> - somehow rebalance data ? >> - add new data after existing ones ? > > Some of the cache will be invalidated, none of it will be migrated between > physical disks. I've added new disk and see that cache has been partially invalidated. Nothing crazy, but still. Anyway, thanks for the answer, I now understand TrafficServer cache more clearly :) Regards, Jean Baptiste
