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.
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:
hostname=* volume=1traffic_ctl metric match volume | grep bytes_usedshould showproxy.process.cache.volume_1.bytes_usedincreasing.hostname=origin.example.org volume=2proxy.process.cache.volume_2.bytes_usedto now increase, however, volume_1 continues to increase instead.proxy.process.cache.volume_2.bytes_usedbegins 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.