[ https://issues.apache.org/jira/browse/RATIS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049180#comment-17049180 ]
Hadoop QA commented on RATIS-814: --------------------------------- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s{color} | {color:blue} Docker mode activated. {color} | | {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 7s{color} | {color:red} RATIS-814 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames for help. {color} | \\ \\ || Subsystem || Report/Notes || | JIRA Issue | RATIS-814 | | Console output | https://builds.apache.org/job/PreCommit-RATIS-Build/1249/console | | Powered by | Apache Yetus 0.8.0 http://yetus.apache.org | This message was automatically generated. > High CPU usage by TimeoutScheduler due to JDK bug JDK-8129861 > ------------------------------------------------------------- > > Key: RATIS-814 > URL: https://issues.apache.org/jira/browse/RATIS-814 > Project: Ratis > Issue Type: Bug > Reporter: Lokesh Jain > Assignee: Lokesh Jain > Priority: Major > Attachments: RATIS-814.001.patch, flamegraph.svg > > > TimeoutScheduler creates an instance of ScheduledThreadPoolExecutor with 0 > core pool threads. There is a bug in JDK > [https://bugs.openjdk.java.net/browse/JDK-8129861] which causes high CPU > usage if ScheduledThreadPoolExecutor is instantiated with 0 core pool > threads. The bug was fixed in Java 9. -- This message was sent by Atlassian Jira (v8.3.4#803005)