Question
Cognizant Technologies Solutions US
CA
Last activity: 9 Feb 2021 19:09 EST
Reg: Admin Studio unable to access
Hello All,
We keep on getting below exception
Caught exception while getting result from future object
java.util.concurrent.TimeoutException: MemberCallableTaskOperation failed to complete within 30 SECONDS. Invocation{op=com.hazelcast.executor.impl.operations.MemberCallableTaskOperation{serviceName='hz:impl:executorService', identityHash=1448080738, partitionId=-1, replicaIndex=0, callId=1600359, invocationTime=1572894865124 (<date>), waitTimeout=-1, callTimeout=60000, name=/pega/system/mgmt/exec}, tryCount=250, tryPauseMillis=500, invokeCount=1, callTimeoutMillis=60000, firstInvocationTimeMs=1572894865159, firstInvocationTime='<date>', lastHeartbeatMillis=1572895458517, lastHeartbeatTime='<date>', target=[**.**.**.**]:5001, pendingResponse={VOID}, backupsAcksExpected=0, backupsAcksReceived=0, connection=Connection[id=23, /:38272->/**.**.**.**:5001, endpoint=[**.***.**.*]:5001, alive=true, type=MEMBER]}
I seen article for similar issue... but its for v8.1.3 please let me know will this be applicable for v8.1.1 ( HFix-51612 given in below article)
Ref: https://community.pega.com/support/support-articles/low-performance-cluster-management-landing-page
Pegasystems Inc.
US
I don't believe there is a hotfix for 8.1.1, the recommended approach would be to upgrade to the latest patch release. For 8.1.x this is resolved starting in 8.1.4 (assuming it's the same issue).
Cognizant Technologies Solutions US
CA
Hello Nick,
Thank you... we will go for upgrade, is there a possibility to check which all nodes didn't joined hazelcast cluster.
UnitedHealth Group
IN
Hello,
I am facing the same issue on Pega 8.2.4 environment which was upgraded yesterday.
Could you please suggest what can be done to fix this?
Cognizant Technologies Solutions US
CA
@RUCHIKUMARI@VarunS19 we upgraded to v8.4.2, now am not seeing this issue anymore. try to truncate pr_sys_context & pr_page_store bring up JVM's it will work.