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

High volume of pr_sys_locks errors when running a campaign

SA-43875

Summary



While running a campaign, a high volume of pr_sys_locks errors occur in a PostgreSQL database consuming a large amount of database processing time.

Note: Across the Cassandra nodes, over 1 million errors in the database logs occur for duplicate key violations on the pr_sys_locks_pk constrain for the (pzinskey)=(STARTUP: DDS.Default) value.


Error Messages

The following message is observed in the database logs (PostgreSQL):

postgresql_20170814_000000.log:
({ID} 23505 {USER} PostgreSQL JDBC Driver) 5990f4b9.4512-1: ({IP ()port)}) ERROR: duplicate key value violates unique constraint "pr_sys_locks_pk"



Steps to Reproduce

  1. Run a large campaign in Pega Marketing
  2. Review database logs

Root Cause

This issue was determined to be a product enhancement request. The errors were caused by the locking mechanism, which locked the startup key every 100 milliseconds.


Resolution

The BUG-327455 was created to review the use of a progressive locking approach to reduce number of database queries.​


Published November 8, 2017 - 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