Thread CPU time is not supported on this JDK – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

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 Elasticsearch operation.

Briefly, this error occurs when Elasticsearch tries to access thread CPU time, but the current Java Development Kit (JDK) version doesn’t support it. This is often due to using an outdated or incompatible JDK version. To resolve this issue, you can upgrade to a newer JDK version that supports thread CPU time. Alternatively, you can disable the usage of thread CPU time in Elasticsearch settings if it’s not crucial for your operations.

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 ” thread CPU time 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 CPU time is not supported on this JDK” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  String innerDetect(ThreadMXBean threadBean; SunThreadInfo sunThreadInfo; long currentThreadId; SleepFunction threadSleep)
 throws Exception {
 if (threadBean.isThreadCpuTimeSupported() == false) {
 throw new ElasticsearchException("thread CPU time is not supported on this JDK");
 }  if (type == ReportType.MEM && sunThreadInfo.isThreadAllocatedMemorySupported() == false) {
 throw new ElasticsearchException("thread allocated memory is not supported on this JDK");


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?