Question
The issue with running more than 6 nodes with Hazelcast
Hi,
We heard from our LeadLSA (who is from Pega) that there will a performance issue when enabling the "HazelCast" in PROD if we have more than 6 nodes. Currently we have 10 nodes running in PROD.
We are implementing a CTI functionality for all our clients, we have to have the hazel cast enable in our PROD to implemented this CTI functionality.
I just need a confirmation from Pega for enabling the HAZELCAST in production environment for 10 Nodes, if there is any issue please let us know along with workaround.
Please find the details from Pega-mesh:
<Removed internal mesh link>
Several places in this thread reference the issue with running more than 6 nodes with hazelcast.
Regards,
Dinesh Kumar.S
***Moderator Edit: Vidyaranjan | Edited internal url***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Adding some reference links below.
https://pdn.pega.com/sites/pdn.pega.com/files/help_v73/engine/Client-se…
https://pdn.pega.com/sites/pdn.pega.com/files/help_v73/procomhelpmain.h… topology/eng-installing-platform-with-client-server-mode-tsk.htm
https://pdn.pega.com/sites/pdn.pega.com/files/help_v73/engine/Client-se…
Hi,
Got the response from PEGA and below is the response from them.
To answer your question about enabling hazelcast for 10 Nodes, please note that there are no such issues per se with the number of nodes in with hazelcast. In fact, you can even have 20, 25 50+ nodes in the cluster. However, if you do encounter any issues, please do not hesitate to submit a new SR, and we'll be more than happy to assist you with any issues you may encounter
By default, Hazelcast is the core/backbone for clustering in PRPC v7.1.9 through v7.3. We have provided Hazelcast specific hotfixes across the above versions to our customers who are running clusters of more than 10 nodes in PRODUCTION and have seen performance issues specifically with Hazelcast.
Starting v7.3, we support both Hazelcast and Apache Ignite. Hazelcast is still the default implementation.
Since Hazelcast doesn't support encryption OOTB, we implemented Ignite so that we could support HIPAA. As of 7.3, we also support an optional client/server configuration in Ignite only when the number of nodes is greater than 6. In a C/S configuration, we have standalone Ignite servers with Pega nodes set up as clients.
The System Pulse will use whichever cluster technology is in use.