Question
Commonwealth Bank of Australia
AU
Last activity: 16 Oct 2018 12:03 EDT
Pega 7.3 Cassandra Setup - Configuring D-Nodes without UI
Greetings,
So I'm in the process of setting up a 7.3 cluster which will contain 3 separate nodes to be allocated for Cassandra. We will be using the Internal Cassandra integration to achieve this.
I understand that once activated via the UI, Cassandra as a process starts on the D-Nodes and goes through a bootstrap process whereby it reads a cassandra.yaml file and combines inputs from prconfig.xml to create the final cassandra.yaml which gets bootstrapped.
But as an Ops person, I need to know how I can configure this without using the UI in order to create a configuration deployment process that is repeatable.
How can I achieve activation and allocation of the D-Nodes via prconfig.xml (and/or other config files) alone? If for whatever reason this is not possible, is there an alternative way I can create a repeatable process?
**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.
Accepted Solution
Commonwealth Bank of Australia
AU
Since nobody else pitched anything usefulw, in prconfig.xml:
<!-- EXPLICITLY ENABLE/DISABLE D-NODE (bool) -->
<env name="initservices/dnode" value="true"/>
<!-- EXPLICITLY ENABLE/DISABLE D-NODE (bool) -->
<!-- CONFIGURE D-NODE DSM SERVICES (list) -->
<!-- e.g. <env name="dsm/services" value="DDS, Dataflow"/ -->
<env name="dsm/services" value=value="DDS, Dataflow"/>
<!-- CONFIGURE D-NODE DSM SERVICES (list) -->
And in terms of the follow up question I asked:
If you want to modify anything in
- cassandra-topology.properties
- cassandra-rackdc.properties
You have crossed the boundary of configuration that Pega will support and the only appropriate pattern is to let the Cassandra cluster to start up and deploy with it's default settings i.e. create the Cassandra directory with it's own default configuration, then you can modify the topology + gossip/snitch stuff making changes in those files suiting your cross site replication and consistency requirements, and then restart the cluster for them to take effect.
Pegasystems Inc.
IN
Hi Christopher,
Kindly go through the below doc to know how you can configure D-Nodes manually.
https://docs-previous.pega.com/decision-strategy-manager-d-node-operations-guide-718
We can use the below configurations in prconfig.xml to setup the nodes:
<env name="cluster/hazelcast/members" value=" Proprietary information hidden, Proprietary information hidden" /> -- list of values, IP
<env name="cluster/hazelcast/members" value=" Proprietary information hidden-99" /> -- range of values (.85-.99)
Please let me know if this helps.
Regards
Vikash
Commonwealth Bank of Australia
AU
In this scenario we will be using Ignite client/server mode over Hazelcast, hence why I was specifically asking for Pega 7.3 information. Should have mentioned that in the question!
Commonwealth Bank of Australia
AU
Okay so to drill a bit down further on this, what do I need to do to ensure I can set values using the following files and where do I need to place my own copies of them to ensure my settings get incorporated when the platform starts up?
- cassandra-env.sh
- cassandra.yaml
- cassandra-topology.yaml
- cassandra-topology.properties
- cassandra-rackdc.properties
Edit: Realistically I will only be touching the first 2, but I want to at least create the ability to modify the settings of the other ones in my deployment logic for other people down the track.
Accepted Solution
Commonwealth Bank of Australia
AU
Since nobody else pitched anything usefulw, in prconfig.xml:
<!-- EXPLICITLY ENABLE/DISABLE D-NODE (bool) -->
<env name="initservices/dnode" value="true"/>
<!-- EXPLICITLY ENABLE/DISABLE D-NODE (bool) -->
<!-- CONFIGURE D-NODE DSM SERVICES (list) -->
<!-- e.g. <env name="dsm/services" value="DDS, Dataflow"/ -->
<env name="dsm/services" value=value="DDS, Dataflow"/>
<!-- CONFIGURE D-NODE DSM SERVICES (list) -->
And in terms of the follow up question I asked:
If you want to modify anything in
- cassandra-topology.properties
- cassandra-rackdc.properties
You have crossed the boundary of configuration that Pega will support and the only appropriate pattern is to let the Cassandra cluster to start up and deploy with it's default settings i.e. create the Cassandra directory with it's own default configuration, then you can modify the topology + gossip/snitch stuff making changes in those files suiting your cross site replication and consistency requirements, and then restart the cluster for them to take effect.