Eric, It is modifying the table schema’s default it will not change existing values.
On 12/4/17, 1:22 PM, "Eric Friedrich (efriedri)" <[email protected]> wrote: It looks like this will modify existing values as well (so its not really a default)? > On Dec 4, 2017, at 3:03 PM, Durfey, Ryan <[email protected]> wrote: > > With the capacity of our servers being in the 18 Gbps range I would say max dns answers should be between 2-4 unless volumes expected are > 250 Gbps. I think 2 or 3 would be a good starting point for most services. > > Ryan Durfey M | 303-524-5099 > CDN Support (24x7): 866-405-2993 or [email protected]<mailto:[email protected]> > > > From: Dylan Volz <[email protected]> > Reply-To: "[email protected]" <[email protected]> > Date: Monday, December 4, 2017 at 12:58 PM > To: "[email protected]" <[email protected]> > Subject: Changing max_dns_answers default > > Hi All, > > The max_dns_answers has been defaulted to 0, which is an unlimited number of answers, which causes issues for deployments with large cache groups. I opened a PR (1611<https://github.com/apache/incubator-trafficcontrol/pull/1611><https://github.com/apache/incubator-trafficcontrol/pull/1611%3e>) to change the default from 0 to 5 which is hopefully a sensible value for most deployments. If this doesn’t seem like a sensible default please respond with alternatives. > > Thanks, > Dylan >
