Thread wait/blocked time accounting is not supported on this JDK – How to solve this Elasticsearch error

Average Read Time

2 Mins

Thread wait/blocked time accounting is not supported on this JDK – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

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: monitor, thread.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “thread wait/blocked time accounting is not supported on this JDK”classname  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=")

 

Watch a demo of the Check-Up:

Analyze your cluster