consul/agent/router
Pierre Souchay 638dcd3360 [BUGFIX] Avoid GetDatacenter* methods to flood Consul servers logs
When calling `GetDatacentersByDistance()` or `GetDatacentersMap()`, an
incorrect condition was used to diplay log message, thus flooding
Consul's logs.

Example of message:

```
  [WARN] agent.router: Non-server in server-only area: non_server=myClientNode area=lan
```

This message is only valid for WAN areas, filter to avoid creating
hundreds of logs/s on our clusters, each time someone is calling this
method.

Our logs were flooded by such messages when migrating our Consul servers
from 1.7.7 to 1.8.4.

This will issue fix #8663
2020-09-15 11:54:59 +02:00
..
manager.go Move RPC router from Client/Server and into BaseDeps (#8559) 2020-08-27 11:23:52 -04:00
manager_internal_test.go Mark its own cluster as healthy when rebalancing. (#8406) 2020-08-06 10:42:09 +02:00
manager_test.go Enable gofmt simplify 2020-06-16 13:21:11 -04:00
router.go [BUGFIX] Avoid GetDatacenter* methods to flood Consul servers logs 2020-09-15 11:54:59 +02:00
router_test.go Move RPC router from Client/Server and into BaseDeps (#8559) 2020-08-27 11:23:52 -04:00
serf_adapter.go Fixed comment on wrong line. 2020-04-24 01:15:15 +02:00
serf_flooder.go network_segments: stop advertising segment tags 2020-05-05 21:32:05 +02:00