Briefly, this error occurs when Elasticsearch is running on a Java Development Kit (JDK) version that does not support thread wait/blocked time accounting. This feature is used by Elasticsearch to monitor and manage thread usage. To resolve this issue, you can either upgrade to a JDK version that supports this feature or disable the thread wait/blocked time accounting in Elasticsearch settings. Alternatively, you can switch to a different JDK distribution that supports this feature.
This guide will help you check for common problems that cause the log ” thread wait/blocked time accounting is not supported on this JDK ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: thread, monitor.
Log Context
Log “thread wait/blocked time accounting is not supported on this JDK” class name is HotThreads.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
} // Enabling thread contention monitoring is required for capturing JVM thread wait/blocked times. If we weren't
// able to enable this functionality during bootstrap; we should not produce HotThreads reports.
if (isThreadWaitBlockTimeMonitoringEnabled(threadBean) == false) {
throw new ElasticsearchException("thread wait/blocked time accounting is not supported on this JDK");
} StringBuilder sb = new StringBuilder().append("Hot threads at ")
.append(DATE_TIME_FORMATTER.format(LocalDateTime.now(Clock.systemUTC())))
.append("; interval=")
[ratemypost]