Seth Rosenblum all time


 0 Collaborator

 2 Patch
fdcd501ad6e434bd3355d0ee6bfb7b61ff5b8f2d, 1762cce65eafd098045e30ef2b7df2c289740971

fdcd501ad6e434bd3355d0ee6bfb7b61ff5b8f2d | Author: Seth Rosenblum <seth@datadoghq.com>
 | 2017-11-28 16:54:39-05:00

    Add myself to authors (#1026)
    
    Forgot as part of #1022

1762cce65eafd098045e30ef2b7df2c289740971 | Author: Seth Rosenblum <seth@datadoghq.com>
 | 2017-11-21 03:54:49-05:00

    Connect to multiple hosts behind a DNS name (#1022)
    
    When using a DNS name as your connection point, this allows the client to attempt to connect to multiple nodes in the cluster when creating the control connection.
    
    We've encountered an issue where our DNS will sometimes return a temporarily offline host first from DNS.  During this time, any client that attempts to bootstrap will return an error as it will only try to connect to that host.  Since we return many hosts in our DNS, the client should attempt to connect to several of them, as if we had passed in a list of IP addresses.