Question

1
Replies
88
Views
Close popover
Ravi Kumar Reddy Kallakunta (reddr2)
PEGA
Lead Decisioning Architect
Pegasystems Inc.
AU
reddr2 Member since 2012 2 posts
PEGA
Posted: January 20, 2020
Last activity: February 9, 2020
Closed

ADM & VBD keyspace issues

Hello All,

@CBA we are upgrading from Pega 7.3 to Pega 8.3.1, found different behavior from Pega 8.3.1.

Pega 7.3 Cassandra Settings with Active/Active Data Centers :

1) prconfig.xml settings

<env name="dnode/yaml/endpoint_snitch" value="GossipingPropertyFileSnitch"/>

<env name="dnode/cassandra_datacenter" value="nwdc"/>

<env name="dnode/default_write_consistency" value="ANY"/>

<env name="dnode/default_read_consistency" value="ONE"/>

2) Cassandra-rackdc.properties file content

dc=nwdc

rack=rack1

with these settings, adm keyspace use to create during the node start up.

with 8.3.1, same settings are resulting different behavior:

1) we are noticing nwdc_adm, nwdc_vbd keyspaces are created by Pega

2) after some time we did notice only adm keyspace also generated not sure why?

couple of questions:

1) why Pega creates datacenter_adm keyspaces for only adm & VBD? not for other keyspaces Pega manages i.e Data/states...

2) why Pega creates datacenter_adm, adm keyspaces?

3) we would already have data accumulated in adm keyspace from 7.3 version- how does this data will be moved into datacenter_adm keyspace?

Thanks,

Ravi

Pega Customer Decision Hub Decision Management
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.