We don't experience downtime when using traffic_ctl config reload (we use that ~daily).
We don't use the balancer plugin. Instead, we use parent.config (https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/parent.config.en.html) to achieve the same consistent hash. Your config would translate to remap.config map / http://127.0.0.1 @plugin=cachekey.so @pparam=--include-params=p0,p1 @pparam=--sort-params=true parent.config dest_domain=. scheme=http parent="123.123.123.1:80,23.123.123.2:80,123.123.123.3:80,123.123.123.4:80" round_robin=consistent_hash go_direct=false dest_domain=. scheme=https parent="123.123.123.1:443,23.123.123.2:443,123.123.123.3:443,123.123.123.4:443" round_robin=consistent_hash go_direct=false miles On Wed, Jan 9, 2019 at 10:53 PM Hobin Yoon <[email protected]> wrote: > > Hi, > > We are noticing there is quite a bit of delay when we reload the config with > traffic_ctl config reload. The delay is up to about 30 seconds, during which > period we don't get any caching. We are using consistency hashing plugin. The > number of nodes changes dynamically between 5 to 30. > > Here is an example balancer (consistent hash) configuration in remap.config. > > map / http://127.0.0.1 @plugin=cachekey.so @pparam=--include-params=p0,p1 > @pparam=--sort-params=true @plugin=balancer.so @pparam=--policy=hash,key > @pparam=123.123.123.1 @pparam=123.123.123.2 @pparam=123.123.123.3 > @pparam=123.123.123.4 ... > > Is this downtime normal? How do you guys avoid the service downtime while > reconfiguring the cache nodes in the cluster? > > Hobin > > > > >
