Collector dns with multiple A records doesn't load balance
With the new collector failover logic we are hoping to rid ourselves of our load balancers all together. However there seems to be a deficiency in the initial connection logic that prevents this. The agent will not try to connect to all address returned from an alias even with multiple A records, it will only try to connect to the first one. This means that if the "first" collector isn't up even though all the other ones are, the agent will not connect to any of them. It's even sillier since the log file is telling me that you know about the multiple addresses but are just using the first one. If this isn't fixed we need to bring the load balancer back solely for making sure our initial connection works!
nslookup result
Name: dyndevcollectors6
Addresses: 10.20.40.173
10.20.40.174
Agent bootstrap log file:
2014-07-24 12:39:27 [00000148] warning [native] Connection::connect(): Address resolution for 'dyndevcollectors6' returned multiple addresses. Using first returned: 10.20.40.174
Hello,
if the collector groups are set up correctly (so all collectors are in the same group), the dynaTrace agent should behave as requested. So if the first collector is not reachable it should try the next one.
In the agent directory there should be a subdirectory "conf" with files like "collectorlist.*". This is the list of collectors the agent should try to connect to. You should see at least on entry per collector of the defined collector group.
Maybe it would be better to open a support ticket with a full support archive to investigate the problem.
Best regards,
Markus
Hi Michael
I will forward this to the engineering team that worked on the load balancing implementation
Andi
