bryancall commented on issue #12069: URL: https://github.com/apache/trafficserver/issues/12069#issuecomment-4828270912
I'm closing this as a stale support request. Traffic Server distributes cached objects across cache stripes (and therefore across disks) by hashing the object's content key, so write and read volume is only as balanced as the distribution of the URLs being cached. If a relatively small set of hot or frequently-updated URLs dominates your traffic, those objects hash to the same stripe and concentrate writes on one or two disks, which matches the large skew you saw between nvme0/nvme1 and nvme2/nvme3. An uneven storage.config or volume.config mapping can produce the same effect. Chris asked for your cache config, volume config, and some sample URLs to dig in further, but we did not hear back, so there is not enough information to investigate this as a bug. If you are still seeing this on a current release, please open a new issue with your storage.config, volume.config, cache.config, and a representative set of request URLs and I would be happy to take another look. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
