Question

3
Replies
340
Views
NigelS42 Member since 2017 3 posts
Link Group
Posted: April 24, 2018
Last activity: April 25, 2018
Closed
Solved

Thread leak in Elastic Search with Pega 7.3.1

There seems to be a thread leak in the version of Elastic Search used by Pega 7.3.1

I have a constant growth in live threads locked against an Elastic Search Reentrant Lock:

Stack Trace:

Name: elasticsearch[73517F73CDA8220A61E5A3C9DDFACF59][generic][T#659]
State: WAITING on java.util.concurrent.locks.ReentrantLock$NonfairSync@7b7ac0f9 owned by: elasticsearch[73517F73CDA8220A61E5A3C9DDFACF59][[unicast_connect]][T#6]
Total blocked: 0  Total waited: 3

Stack trace: 
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209)
java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285)
org.elasticsearch.common.util.concurrent.KeyedLock.acquire(KeyedLock.java:70)
org.elasticsearch.transport.netty.NettyTransport.disconnectFromNode(NettyTransport.java:1078)
org.elasticsearch.transport.TransportService.disconnectFromNode(TransportService.java:274)
org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$2$1.doRun(UnicastZenPing.java:258)
org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)

This is possibly a known issue, although I'm not sure that cluster members are joining / leaving that frequently:

https://github.com/elastic/elasticsearch/issues/8057

Moderation Team has archived post
Share this page LinkedIn