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 OpenSearch is trying to send an extension request but encounters an issue. This could be due to network problems, incorrect configuration, or the extension not being properly installed or supported. To resolve this, you can check your network connection, verify the configuration settings, or ensure the extension is correctly installed and compatible with your OpenSearch version. If the problem persists, consider disabling the extension temporarily to see if it’s the cause of the issue.
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 ” Sending extension request type: ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: request.
Log Context
Log “Sending extension request type:” classname is ExtensionsManager.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
public String executor() {
return ThreadPool.Names.GENERIC;
}
};
logger.info("Sending extension request type: " + REQUEST_EXTENSION_ACTION_NAME);
transportService.getThreadPool().generic().execute(new AbstractRunnable() {
@Override
public void onFailure(Exception e) {
extensionIdMap.remove(extension.getId());
if (e.getCause() instanceof ConnectTransportException) {
