v8.7 confusion of the use of embedded kafka, cassandra/support
87_PlatformSupportGuide_Jan2022.pdf - below is mentioned in the doc.
1. Beginning in Pega Platform version 8.6, when you are setting up new environments, you are encouraged to use an external Cassandra database instead of the embedded version
In Pega Platform version 8.6, deployments using embedded Cassandra are deprecated, but will still work. Future versions of Pega Platform will no longer support deployments on embedded Cassandra.
To ensure future compatibility, do not create any new installations using embedded Cassandra.
For information about how to configure Pega Platform to access an external database, see Defining Pega Platform access to an external Cassandra database.
2. Same with embedded kafka in the 8.7 release note - https://docs-previous.pega.com/platform-release-notes/87/platform-87-release-notes
Questions:
1. For earlier version that are currently using embedded Cassadran and Kafka, is it a pre-requisite to provision External Cassandra and External Kafka? 2. what is going to happen if the client does not have the Cassandra and Kafka server set up 3. is the stream nodetype still be there but for internal use?
If no more embedded Kafka, how would this impact QP and Search Indexing that are currently using stream node? 4. is the DDS nodetype still be there but for internal use?
87_PlatformSupportGuide_Jan2022.pdf - below is mentioned in the doc.
1. Beginning in Pega Platform version 8.6, when you are setting up new environments, you are encouraged to use an external Cassandra database instead of the embedded version
In Pega Platform version 8.6, deployments using embedded Cassandra are deprecated, but will still work. Future versions of Pega Platform will no longer support deployments on embedded Cassandra.
To ensure future compatibility, do not create any new installations using embedded Cassandra.
For information about how to configure Pega Platform to access an external database, see Defining Pega Platform access to an external Cassandra database.
2. Same with embedded kafka in the 8.7 release note - https://docs-previous.pega.com/platform-release-notes/87/platform-87-release-notes
Questions:
1. For earlier version that are currently using embedded Cassadran and Kafka, is it a pre-requisite to provision External Cassandra and External Kafka? 2. what is going to happen if the client does not have the Cassandra and Kafka server set up 3. is the stream nodetype still be there but for internal use?
If no more embedded Kafka, how would this impact QP and Search Indexing that are currently using stream node? 4. is the DDS nodetype still be there but for internal use?
If no embedded Cassandra, how would this impact ADM and DSM that are currently using embedded Cassandra?
Unisys Australia Propriety Ltd
AU
@chars1 have you got any answers to your questions. I am also getting confused as it is mentioned in the support guide for 8.7 it says it support embeded cassandra in table added as attachment but also mentioned that we should use external cassandra for new deployments. So my question is does 8.7 support embeded cassandra ?
Pegasystems Inc.
AU
@jatenders7882 - no luck so far. Plus, my client has many Pega platforms and if they are going to share the same Kafka Server for example or Cassandra Server, Are they going to have crashing topic names or table names?
Updated: 22 Feb 2022 4:37 EST
Pegasystems Inc.
AU
@jatenders7882 - I believe that we better prepare for hosting those services outside as client/server mode as most clients are setting their own private cloud via EKS / ECS. This would help with the shared External Kafka topics by many projects and environments.
https://community.pega.com/node/2187636
An enhancement has been added to support the use of site-specific standards for the naming of queues. This can be used to add clarification between Kafka Topics created by Pega and those created for internal topics when using a shared Kafka Cluster. This is done using the new setting: <env name=”services/stream/name/pattern” value=”prefix{stream.name}postfix”/>
.As an example, if tenant.name is resolved into "myco" and the environment into "prod1", value="{tenant.name}-{environment}-{stream.name}" will result in stream myco-prod1-{stream.name} By default, when stream.provider = EXTERNAL, the default will be “pega-{stream.name}” .
Resolved in Product Version 8.5
@jatenders7882 - I believe that we better prepare for hosting those services outside as client/server mode as most clients are setting their own private cloud via EKS / ECS. This would help with the shared External Kafka topics by many projects and environments.
https://community.pega.com/node/2187636
An enhancement has been added to support the use of site-specific standards for the naming of queues. This can be used to add clarification between Kafka Topics created by Pega and those created for internal topics when using a shared Kafka Cluster. This is done using the new setting: <env name=”services/stream/name/pattern” value=”prefix{stream.name}postfix”/>
.As an example, if tenant.name is resolved into "myco" and the environment into "prod1", value="{tenant.name}-{environment}-{stream.name}" will result in stream myco-prod1-{stream.name} By default, when stream.provider = EXTERNAL, the default will be “pega-{stream.name}” .
Resolved in Product Version 8.5
//--------------- for Cassandra if you need to get this hosted outside and share the Cassandra cluster/ring with multiple projects https://collaborate.pega.com/question/connecting-multiple-pega-clusters-single-cassandra-ring setting a prconfig on each environment: dnode/keyspaces_prefix. By defining a unique prefix for each environment, each one would create its own set of keyspaces and would not access each other's data (keyspace names will no longer clash).
Updated: 28 Mar 2022 10:04 EDT
Nordea
SE
did you get answer to your questions. seems this question is being raised by many customers and pega should clarify it. The current installation/upgrade guide does not seem to provide much info.