Update Opensearch to 2.10 and change OpenJDK to 17
Diff Detail
Diff Detail
- Lint
Lint Skipped - Unit
Tests Skipped
Event Timeline
Comment Actions
I was testing opensearch 2.10.0 with OpenJDK 17 and it is generating lot of WARN messages
[2023-09-29T01:01:21,765][WARN ][o.o.t.TaskManager ] [indexer1] Failed to mark thread execution started for task: [74979]
java.lang.UnsupportedOperationException: Thread CPU time measurement is not supported.
at sun.management.ThreadImpl.verifyThreadCpuTime(ThreadImpl.java:258) ~[?:?] at sun.management.ThreadImpl.getThreadCpuTime(ThreadImpl.java:277) ~[?:?] at com.sun.management.internal.HotSpotThreadImpl.getThreadCpuTime(HotSpotThreadImpl.java:52) ~[?:?] at sun.management.ThreadImpl.getThreadCpuTime(ThreadImpl.java:248) ~[?:?] at org.opensearch.tasks.TaskResourceTrackingService.getResourceUsageMetricsForThread(TaskResourceTrackingService.java:219) ~[opensearch-2.10.0.jar:2.10.0] at org.opensearch.tasks.TaskResourceTrackingService.taskExecutionStartedOnThread(TaskResourceTrackingService.java:181) [opensearch-2.10.0.jar:2.10.0] at org.opensearch.threadpool.TaskAwareRunnable.doRun(TaskAwareRunnable.java:73) [opensearch-2.10.0.jar:2.10.0] at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52) [opensearch-2.10.0.jar:2.10.0] at org.opensearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:59) [opensearch-2.10.0.jar:2.10.0] at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:908) [opensearch-2.10.0.jar:2.10.0] at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52) [opensearch-2.10.0.jar:2.10.0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?] at java.lang.Thread.run(Thread.java:833) [?:?]
I think we should keep on JAVA_VERSION=11+ until opensearch project apply some kind of patch file to fix the issue. Using OpenJDK 11 WARN messages are not showed. You can look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263881 I think it is related to this issue