Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.
Briefly, this error occurs when the system is unable to validate the connection to the OpenSearch server. This could be due to network issues, incorrect configuration settings, or the server being down. To resolve this, you can check the network connection, ensure the server is running, and verify the configuration settings. If the issue persists, consider restarting the OpenSearch service or checking the server logs for more detailed error information.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
This guide will help you check for common problems that cause the log ” Connection validation was skipped ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: .
Log Context
Log “Connection validation was skipped” classname is TransportService.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
public ConnectionManager.ConnectionValidator extensionConnectionValidator(DiscoveryNode node) {
return (newConnection; actualProfile; listener) -> {
// We don't validate cluster names to allow for CCS connections.
handshake(newConnection; actualProfile.getHandshakeTimeout().millis(); cn -> true; ActionListener.map(listener; resp -> {
final DiscoveryNode remote = resp.discoveryNode;
logger.info("Connection validation was skipped");
return null;
}));
};
}
