Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Campaign run fails with an error when a DDS node stops

SA-73251

Summary


 

In a production environment with 10 Decision Data Store (DDS) nodes, user runs a campaign. The campaign run fails with an error if one of the DDS nodes stops during the campaign run.


Error Messages


 

com.pega.dsm.dnode.api.ExceptionWithInputRecord: Could not save record of class [SR] to a Data Set with applies to class [SR] at com.pega.dsm.dnode.impl.dataset.SaveWithTTLOperation$4.emit(SaveWithTTLOperation.java:263) at com.pega.dsm.dnode.impl.dataset DataEmitter.emit(DataEmitter.java:54) at com.pega.dsm.dnode.impl.prpc.PrpcThreadFactory$PrpcThread.run(PrpcThreadFactory.java:109) Caused by: java.util.concurrent.ExecutionException: com.datastax.driver.core.exceptions.TransportException: Connection has been closed at util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:476) at concurrent.AbstractFuture.get(AbstractFuture.java:357) at haveWithTTLOperation$SaveFuture.get(SaveWithTTLOperation.java:487) 

 

Steps to Reproduce


 

1. Configure multiple DDS nodes in a Cassandra cluster
2. Create a campaign
3. Stop one of the DDS nodes during the campaign run


Root Cause



A defect in Pegasystems’ code or rules. 

Resolution



Apply HFix-50796.

 

Published March 12, 2019 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us