Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

2018-02-13 Thread Steve Malenfant
Jesse, I'm not exactly sure how MaxMind return this default value but would there be a way to use the MISS location specified in the DS? Seems like that is what it was intended for. Steve On Tue, Feb 13, 2018 at 12:42 PM, Rivas, Jesse wrote: > Hi all, > > > > At

Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

2018-02-13 Thread Rivas, Jesse
Steve, Using the miss location for the DS was a potential solution that we talked about. However, the miss location is intended for use when the client IP falls through MaxMind without any data. Since the default location doesn't fit this criteria, it was decided to use a profile parameter to

Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

2018-02-13 Thread Rivas, Jesse
Above I mentioned that the parameter 'maxmind.default.override' supports multiple entries so that there can be override coordinates for more than one country. To be more specific, the user can add multiple parameters using the same key to create multiple entries. Jesse On 2/13/18, 10:51 AM,

Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

2018-02-13 Thread Rawlin Peters
Yeah, this basically solves the problem where MaxMind knows a client is in the US (or another country) but doesn't know the state, city, zip, etc., so it's not a "true" miss. In that case MaxMind returns the geographic center of that country as the client's location, but we don't want to route

Traffic Router Enhancement - Default Maxmind Geolocation Override

2018-02-13 Thread Rivas, Jesse
Hi all, At Comcast, we have been seeing a pattern of the same cache group being overloaded nightly as traffic increases on the CDN. The cause was determined to be a default location that the geolocation provider MaxMind returns for client IPs that it does not have additional data for. For

Re: Connection leaks traffic stats -> influxdb

2018-02-13 Thread Steve Malenfant
Nir, We have observed this in the past as well. We are still running traffic_stats 2.1.0 and using this cronjob as workaround for now. $ cat /etc/cron.d/traffic_stats_restart #Ansible: Restart Traffic Stats 0 8 * * * root /etc/init.d/traffic_stats restart >/dev/null 2>&1 Steve On Mon, Feb

Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

2018-02-13 Thread Nir Sopher
Hi, Can this solution support different value in different routers? Taking TR localization into account, it might give better granularity. Nir On Tue, Feb 13, 2018 at 8:34 PM, Rawlin Peters wrote: > Yeah, this basically solves the problem where MaxMind knows a client

[VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC0

2018-02-13 Thread Robert Butts
Hello All, I've prepared a release for v2.2.0-RC0 The vote is open for at least 72 hours and passes if a majority of at least 3 +1 PPMC votes are cast. [ ] +1 Approve the release [ ] -1 Do not release this package because ... Changes since 2.1.0:

Immutable DS CDN - resolving Riak/Postgres data coherency

2018-02-13 Thread Nir Sopher
Hi, I created a delivery service and later on realized it is in the wrong CDN. I then changed the CDN. The ssl-keys record in the riak kept referring to the old CDN, even if I generated new certificates. Traffic router was therefore unable to pull the certificate. See issue 1847

Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

2018-02-13 Thread Rivas, Jesse
Nir, This solution does not support that level of granularity. Jesse On 2/13/18, 11:43 AM, "Nir Sopher" wrote: Hi, Can this solution support different value in different routers? Taking TR localization into account, it might give better granularity.

Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

2018-02-13 Thread Rawlin Peters
Nir, You bring up a good point. If we can make the assumption that requests coming to a specific Traffic Router are actually somewhat local to that Traffic Router, we might be able to localize those "country-localized" clients to a cachegroup close to that particular Traffic Router. That would

Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC0

2018-02-13 Thread Jeff Elsloo
-1 due to the following PR breaking the Traffic Router build: https://github.com/apache/incubator-trafficcontrol/pull/1720 I'm looking into the issue now and hope to have it resolved soon. -- Thanks, Jeff On Tue, Feb 13, 2018 at 11:56 AM, Robert Butts wrote: > Hello All, > >

Re: Connection leaks traffic stats -> influxdb

2018-02-13 Thread Nir Sopher
Thanks Steve :) Dave, I see it on master as well... Thanks! Nir On Tue, Feb 13, 2018 at 8:02 PM, Steve Malenfant wrote: > Nir, > > We have observed this in the past as well. We are still running > traffic_stats 2.1.0 and using this cronjob as workaround for now. > > $ cat

Re: Immutable DS CDN - resolving Riak/Postgres data coherency

2018-02-13 Thread Dave Neuman
I think I can get on board with not allowing a user to change the CDN. If you want to change the CDN you need to delete your DS and re-create it or create a new DS with a different XML_ID and a regex that matches the first DS. We have gone back and forth several times on deleting the keys from

Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC0

2018-02-13 Thread Jeff Elsloo
I just submitted the following PR to resolve the issues stemming from PR 1720: https://github.com/apache/incubator-trafficcontrol/pull/1877 -- Thanks, Jeff On Tue, Feb 13, 2018 at 3:25 PM, Jeff Elsloo wrote: > -1 due to the following PR breaking the Traffic Router build: >

Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC0

2018-02-13 Thread Dave Neuman
Hey Jeff, I can take a look at that PR. Thanks, Dave On Tue, Feb 13, 2018 at 4:15 PM, Jeff Elsloo wrote: > I just submitted the following PR to resolve the issues stemming from > PR 1720: https://github.com/apache/incubator-trafficcontrol/pull/1877 > -- > Thanks, > Jeff > > >

Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC0

2018-02-13 Thread Chris Lemmons
-1 due to some licensing issues: - traffic_ops/testing/compare/vendor/github.com/kelseyhightower/envconfig is not identified as non-Apache licensed in the LICENSE file. - traffic_ops/testing/compare/vendor/github.com/x/net is not identified as non-Apache licensed in the LICENSE file. These