Hi 

Please see responses below from the Decisioning product team.

Does 7.3.1 supports multi data center configurations

Yes, with Hfix-41762 (Notes on adding a second DSM center have previously bee shared with you)

Without DC awareness, is it feasible to do node repair

— not sure what is the question about, I'd say yes — 

What is the Consistency level to be configured

By default Pega use consistency level ONE, there is no need to modify it. 

Is it always required to define multiple racks?

No.

If we have replication factor as 3 and we have multiple data centres, what is the Replication factor that we need to configure on each data centre?

When replication factor is set to 3 and instruction above is followed, it is set to 3 for each datacenter. If one needs to restrict a keyspace to only one datacenter, it can be set using prconfig: dnode/cassandra_local_datacenter_keyspaces. In 7.3.1 by default only ADM keyspace is set as local.

For more details around racks and replication, see https://docs.datastax.com/en/cassandra/3.0/cassandra/architecture/archDataDistributeReplication.html 

In a multi data centre if one data centre is down, will it allow us to truncate the Cassandra table

No, the cluster needs to be in consistent state to truncate table.

Let me know if you have any queries or concerns.

Additional questions:

·         We need to have discussions regarding the version of Cassandra that they distribute and support with Pega, given that v2.1.x appears to be nearing end-of-life in terms of receiving any critical fixes

·         We should ask Pega, whether other Pega customers are successfully using ‘external’ Cassandra v3.11.x clusters – with encryption / authentication and data center awareness configured.

o    Will Pega support on using external version?

o    Any detailed documentation available for external cassandra setup ?

o    Will Pega considering formally move on to later version of cassandra in near future?

·         Should confirm with Pega, as stated in their support documentation, that they will continue to support any issues with Pega functionalities that utilise an ‘external’ Cassandra cluster.

Please advise...

Hi ,

Please find my responses below,

We should ask Pega, whether other Pega customers are successfully using ‘external’ Cassandra v3.11.x clusters – with encryption / authentication and data center awareness configured.

Yes

o    Will Pega support on using external version?

https://community.pega.com/knowledgebase/articles/techniques-integrating-cassandra-your-application

As mentioned in the note in the link, 

Pega Platform supports connections with external Cassandra in version 2.1 or higher.

o    Any detailed documentation available for external cassandra setup ?

Should confirm with Pega, as stated in their support documentation, that they will continue to support any issues with Pega functionalities that utilise an ‘external’ Cassandra cluster.

Yes

Hi

1. we are using Pega v7.3.1 platform and can you confirm which version of the DataStax Cassandra Java driver using?

I’ve been referring to this …

https://docs.datastax.com/en/developer/java-driver/3.1/manual/ssl/

2. Are there any  prconfig, or DSS, or env  related SSL settings when calling the drivers as per above point?

Please advise. Thanks

Hi, We are getting this error using SSL auth enabled on Cass v3.11.X nodes using external setup mechanism.

ERROR [epollEventLoopGroup-2-4] 2019-02-06 16:36:30,859 Message.java:629 - Unexpected exception during request; channel = [id: 0x2e025f63, L:/11.159.165.248:9042 ! R:/11.159.165.232:44430]

io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: null cert chain

When we checked PDN article, we have come across this article below

https://community1.pega.com/node/1383896

Can you advise what next steps to follow?