Question
ING Belgium SA NV
BE
Last activity: 18 Oct 2018 9:51 EDT
clustering topology- Apache ignite vs hazlecast
Hi,
Pega upgrade from 7.1.9 to 7.3.1 is planned for our application. when i go through upgrade, i could see the option to determine the topology either hazlecast or apache ignite.
1.Kindly advise on difference between both of them?
2.which is recommended for 4 nodes cluster?
3. how do i confirm that which topology/method is used by my application?
4.what are all the things we should note down on clustering topology during upgrade?
Reference : Pega 7.3.1 upgrade guide
Pegasystems Inc.
IN
Hi,
Main difference between hazel cast and Apache Ignite are below:
1.Apache Ignite supports group-indexes and SQL JOINs across different caches or data types which is not provided by Hazel cast
2.Apache Ignite indexing is a lot more sophisticated than Hazel cast. Apache Ignite supports ANSI 99 SQL.
ING Belgium SA NV
BE
Thanks for your reply. could you please reply on below points also to get better understanding?
3. how do i confirm that which topology/method is used by my application?
4.what are all the things we should note down on clustering topology during upgrade?
Pegasystems Inc.
IN
We can set the clustering topology to be used by application server nodes through below prconfig setting.
<env name="identification/cluster/protocol" value="ignite“/>
Equivalent DSS:prconfig/identification/cluster/protocol/default (here node classification is default)
Owning Ruleset: Pega-Engine
Value: ignite or hazelcast
Value can be hazelcast or ignite. Default is hazelcast.
From 7.3, you can use ignite.
Depending on your requirement, you can chose which topology you wish to use and use the deployment(upgrade/update/installation) guide for steps to follow to configure clustering.
Ernst & Young
LU
Hi. Thanks for your reply.
I could see 2 DASS setting in Pega-Engine ruleset, but not prconfig/identification/cluster/protocol/default (here node classification is default). prconfig/identification/cluster/name
prconfig/identification/systemName/default.
Checked in prconfig setting as well. There is no tags related to clustering protocol. We are using 7.1.9 version now. Kindly advise.
Pegasystems Inc.
IN
In 7.1.9, default is hazelcast.
Even if this setting is not there in DSS or prconfig, default will be hazelcast.
You can use this setting(prconfig or DSS) to override the value of the setting(value can be database or hazelcast).
It is strongly recommended that you use hazelcast and not database.
Ignite is available from 7.3
Pegasystems Inc.
AU
You would ideally make use of Apache ignite if you have very large multi node cluster.
Use Apache ignite for large production environments that consist of more than five cluster nodes or if you experience cluster instability even in clusters that contain fewer nodes. The number of nodes in the cluster that can lead to cluster instability depends on your environment, and switching to client-server mode is determined individually.
UnitedHealth Group
IN
My application is using 32 JVM and working on migration from Pega 7.1.9 to 7.4. As part of this migration we in process of evaluating Hazelcast vs Apache ignite.
1. Can we have some more details comparison between Hazel Cast vs Apache Ignite.
2. Do we need any additional hardware to use Apache ignite
Pegasystems Inc.
US