java.util.concurrent.CancellationException: Task was cancelled
CancellationException is generated in the logs.
java.util.concurrent.CancellationException: Task was cancelled.
Steps to Reproduce
The unique identifier for the node changed unexpectedly. One of nodes in the cluster was terminated. Hazelcast changed the unique identifier as part of its cluster Merge process or Split Brain resolution process.
The request hit Node 1 and attempted to connect to Nodes 2 and 3. However, it was unable to. Node 1 was formed on a cluster since Hazelcast was configured to connect indefinitely and continued to search for Nodes 2 and 3. These nodes were not found and the system of records was updated. Hence, the exception was generated.
Perform the following local-change:
- Truncate the pr_sys_statusnodes table.
- Clear the cache on all nodes (PegaAppTier and PegaUtilTier).
- Restart all the nodes.
0% found this useful