Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).
This guide will help you check for common problems that cause the log ” Took . which is over . to for ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster and master.
Log Context
Log “took [{}]; which is over [{}]; to {} for [{}]” classname is MasterService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
}
private void logExecutionTime(TimeValue executionTime; String activity; String summary) {
if (executionTime.getMillis() > slowTaskLoggingThreshold.getMillis()) {
logger.warn("took [{}]; which is over [{}]; to {} for [{}]"; executionTime; slowTaskLoggingThreshold; activity; summary);
} else {
logger.debug("took [{}] to {} for [{}]"; executionTime; activity; summary);
}
}
Find & fix Elasticsearch problems
