Refreshing host metadata does not account for custom address resolver
Description
The custom_address_resolution feature failed in a recent build, and it seems the issue is that if a host-metadata refresh is required, the driver doesn't invoke the address resolver to determine the ip from the driver's perspective. This results in an extra Host object being recorded in the registry and may cause unfairness in the load-balancing policy (as there are two Host's for the same node).
The custom_address_resolution feature failed in a recent build, and it seems the issue is that if a host-metadata refresh is required, the driver doesn't invoke the address resolver to determine the ip from the driver's perspective. This results in an extra Host object being recorded in the registry and may cause unfairness in the load-balancing policy (as there are two Host's for the same node).