NETWORKING: Make RemoteClusterConn. Lazy Resolve DNS (#32764) #32976
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
StringtoDiscoveryNode) to not run into indefinitely caching lookup issues (provided the JVM dns cache is configured correctly as explained in https://www.elastic.co/guide/en/elasticsearch/reference/6.3/networkaddress-cache-ttl.html)InetAddresstype toStringfor that higher up the stackSupplier<DiscoveryNode>instead of outrightDiscoveryNodefromRemoteClusterAware#buildRemoteClustersSeedson to lazy resolve DNS when theDiscoveryNodeis actually used (could've also passed down the value ofclusterName = REMOTE_CLUSTERS_SEEDS.getNamespace(concreteSetting)together with theList<String>of hosts, but this route seemed to introduce less duplication and resulted in a significantly smaller changeset).Backport PR just to run Jenkins