The disruption tests try to simulate various pauses that could occur within ES. One of these possible pauses is a GC pause. The disruption tests simulate GC pauses using Thread suspend/resume. However, in JDK 20, Thread suspend/resume now throws UnsupportedOperationException (those methods have been deprecated since JDK 1.2, and are slated for permanent removal).
We should rethink how to simulate GC pauses (perhaps with external jvm control like JVMTI), or more broadly whether the disruption tests still provide value (they are complicated and have been flaky in the past).
The disruption tests try to simulate various pauses that could occur within ES. One of these possible pauses is a GC pause. The disruption tests simulate GC pauses using Thread suspend/resume. However, in JDK 20, Thread suspend/resume now throws UnsupportedOperationException (those methods have been deprecated since JDK 1.2, and are slated for permanent removal).
We should rethink how to simulate GC pauses (perhaps with external jvm control like JVMTI), or more broadly whether the disruption tests still provide value (they are complicated and have been flaky in the past).