OperationalTimeoutException occurs and system does not respond
Executing multiple extracts from the Business Intelligence Exchange (BIX) Command Line impacts users on other nodes.
Caused by: com.hazelcast.core.OperationTimeoutException: QueryPartitionOperation got rejected before execution due to not starting within the operation-call-timeout of: 60000 ms.
Caused by: com.hazelcast.core.OperationTimeoutException: CacheGetOperation got rejected before execution due to not starting within the operation-call-timeout of: 60000 ms.
Steps to Reproduce
Execute multiple extracts in parallel from the Command Line.
A defect or configuration issue in the operating environment.
Each BIX extraction from the Command Line starts and stops PegaEngine nstance which in turn is added and removed from the Hazelcast cluster. Executing multiple extracts in parallel means that there are multiple new members joining and leaving the cluster at the same time. As a result, the utility node performance degraded. Additionally, while the extractions are running, they are querying for the work tables used.
Perform the following local-change:
For the BIX extracts, add the below code to the prconfig.xml file which the BIX Command Line process uses to prevent Hazelcast from communicating with other nodes. <env name="identification/cluster/protocol" value="standalone" />
- Apply HFix-50824.
- Apply HFix-46681 (to upgrade to Hazelcast 3.10 EE).
0% found this useful