Etienne Chauchot created BEAM-3119:
--------------------------------------
Summary: direct-metrics-counter-committer threads might be leaking
Key: BEAM-3119
URL: https://issues.apache.org/jira/browse/BEAM-3119
Project: Beam
Issue Type: Bug
Components: runner-direct
Reporter: Etienne Chauchot
Assignee: Thomas Groh
When I run ElasticsearchIOTests using ESv5, there is a thread leak control
mechanism ({{com.carrotsearch.randomizedtesting.ThreadLeakControl}}). It waits
for 5s for non-terminated threads at the end of a test. It detects leaked
{{direct-metrics-counter-committer}} thread.
{code}
com.carrotsearch.randomizedtesting.ThreadLeakError: There are still zombie
threads that couldn't be terminated:
1) Thread[id=296, name=direct-metrics-counter-committer,
state=TIMED_WAITING, group=TGRP-ElasticsearchIOTest]
at sun.misc.Unsafe.park(Native Method)
at
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at
java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
at
java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:362)
at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:941)
at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1066)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at __randomizedtesting.SeedInfo.seed([59E504CA1B0DD6A8]:0){code}
I tried to increase the timeout to 30s (by patching
randomizedtesting-runner-2.5.0.jar) but still gets a zombie thread.
To reproduce, just comment
{code}
@ThreadLeakScope(ThreadLeakScope.Scope.NONE)
{code}
in
{code}
beam/sdks/java/io/elasticsearch-tests/elasticsearch-tests-5/src/test/java/org/apache/beam/sdk/io/elasticsearch/ElasticsearchIOTest.java
{code}
and run
{code}
testRead()
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
