Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Thread Dumps display when operators execute a Full text Search

SA-68704

Summary



System displays Thread Dumps intermittently when operators execute a Full text Search. The system consists of a cluster with four nodes with one Search or an Index node.


Error Messages



"tomcat-lrv171q7--37" Id=190 in WAITING on lock=org.elasticsearch.common.util.concurrent.BaseFuture[email protected]
BlockedCount : 1781, BlockedTime : -1, WaitedCount : 58797, WaitedTime : -1
    at sun.misc.Unsafe.park(Native Method)
    at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
    at org.elasticsearch.common.util.concurrent.BaseFuture$Sync.get(BaseFuture.java:280)
    at org.elasticsearch.common.util.concurrent.BaseFuture.get(BaseFuture.java:120)
    at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:42)
    at com.pega.pegarules.search.internal.es.FTSQueryExecutor.executeQuery(FTSQueryExecutor.java:158)
    at com.pega.pegarules.search.internal.es.FTSQueryExecutor.executeQuery(FTSQueryExecutor.java:80)
    at com.pega.pegarules.search.internal.es.FTSContentExecutor.executeGenericQuery(FTSContentExecutor.java:197)
    at com.pega.pegarules.search.internal.es.FTSContentExecutor.executeQuery(FTSContentExecutor.java:170)
    at com.pega.pegarules.search.internal.es.FTSContentExecutor.executeSearchQuery(FTSContentExecutor.java:127)



Steps to Reproduce



Not Applicable


Root Cause

The Thread Dump occurred because the system had insufficient capacity to cope with the resource intensive search operation.

For more information, refer to: https://community.pega.com/support/support-articles/performance-degrades-elastic-search

According to the Online Help document, in a multinode cluster system, the index files required for a search can be hosted on one or more nodes. To ensure high reliability and minimize search query downtime, configure at least two, and preferably three nodes as search host nodes.





Resolution



Perform the following local-change to accommodate a resource intensive Search operation:

Reconfigure the system with multiple Search or Index nodes.



 

Published December 12, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us