On Sep 15, 2013, at 11:27 AM, Leif Hedstrom <zw...@apache.org> wrote:
> On Sep 14, 2013, at 4:30 PM, James Peach <jpe...@apache.org> wrote: > >> On Sep 13, 2013, at 8:12 PM, Yongming Zhao <ming....@gmail.com> wrote: >> >>> I'd like we can get more known of all the confusing problems we have, I >>> don't have any conclusion or suggestion at all. >>> >>> >>> here is my known of the 'traffic_line -x', it is the central control of >>> taking config update in to running, when you changed the records.config >>> with VIM for example. >>> but we have some problem here too: >>> 1, there is 'traffic_line -s xx -v yy', which will take into action without >>> any hesitate. >>> 2, if you changed your plugin so, or plugin.config, it won't get in update >>> at all, for example TS-2104. >>> >>> here, we use rpm to manage the ATS binary and plugins, we find it not so >>> easy for plugin management too. the plugin is a lightweight change in our >>> daily management, we'd not like to restart ATS. >> >> I have some ideas about how to do a graceful restart of ATS so that plugins >> could be reloaded without dropping any connections. Not sure whether there >> is a ticket on it. I hope to work on it this year. > > > Would that retain e.g. the RAM cache across restarts? Not in the first version, but it's probably possible. > I like this idea a lot, for things such as server or plugin code upgrades. > But is it really the best approach for something you might do very > frequently, such as reloading plugin configs? No, it's primarily for reloading code (plugin and ATS upgrades). > I think that better APIs and infrastructure to let all configs, including > plugins, reload gracefully and at close to zero cost is a good idea too. Yes, +10 J
