mlibbey opened a new issue #7220: URL: https://github.com/apache/trafficserver/issues/7220
Docs say that hosting.config changes are reloadable: https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/hosting.config.en.html "After you modify hosting.config, navigate to the Traffic Server bin directory and run traffic_ctl config reload to apply your changes." This line has been in the docs since the initial release. In testing, we observe that changes to hosting.config only take effect after restart. The best way I've found to see this: - make a host with 2 volumes. In hosting.config have ```hostname=* volume=1``` - after starting up, fetch objects. ```traffic_ctl metric match volume | grep bytes_used``` should show ```proxy.process.cache.volume_1.bytes_used``` increasing. - edit hosting.config, adding the origin (for example ```hostname=origin.example.org volume=2``` - reload trafficserver - fetch more objects. You'd expect ```proxy.process.cache.volume_2.bytes_used``` to now increase, however, volume_1 continues to increase instead. - Upon restart and more fetches, ```proxy.process.cache.volume_2.bytes_used``` begins increasing. Our primary use case for the hosting.config is to assign "properties" that either have low max-age or useful lifetime (for instance a live sports stat object may be constantly updated; a live video segment is only fetched in a small time window). Being able to dynamically add such use cases would be useful. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
