bdacheckcluster Extremely Slow and Errors Raised Checking DNS Resolve for One Hostname
Last updated on DECEMBER 05, 2016
Applies to:Big Data Appliance Integrated Software - Version 4.2.0 and later
Running bdacheckcluster is so slow it appears to be hung. Along with this one node of the cluster can not have its public hostname resolved.
1. Running bdacheckcluster produces errors when "Checking local DNS resolve of public hostnames on all cluster hosts" for one node of the cluster. In other words we see that one node of the cluster, for example bdanode01.example.com, can not be resolved on any node of the cluster.
This step does not take excessive time, but errors out. The error shows that when executing "host bdanode01.example.com" the client address is returned
not the private address as expected.
a) bdacheckcluster error for bdanode01 when "Checking local DNS resolve of public hostnames on all cluster hosts":
These lookups are supposed to be fast because they should not be accessing any nameserver. However any slowdown will be amplified by cross-host checking.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms