Posted: 1 Aug 2017 20:28 EDT Last activity: 16 Oct 2018 12:03 EDT
Pega 7.3 Cassandra Setup - Configuring D-Nodes without UI
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.
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?
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.
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.