We are experiencing row lock contention on the ACT_GE_PROPERTY table when running Camunda 7.15 Community Edition on Oracle 19c. The application is deployed in a Kubernetes environment with a scalable multi-pod architecture.
The Advanced Workload Repository (AWR) report highlights the following SQL statement causing the contention:
INSERT INTO ACT_GE_PROPERTY (name_, value_, rev_)
VALUES (:1, :2, 1)
Any idea on this issue?
Hello my friend!
This seems to be a concurrency situation, maybe you need to configure something to synchronize access, since multiple pods may be trying to update the same table.
When multiple Camunda instances are running in multiple pods you may have problems like this, but maybe you can configure something like a “Leader election” to configure a single pod as leader… Spring itself has a Kubernetes library for this, and the configuration can be done through application.yml.
Hope this helps.
William Robert Alves
Thank you for the reply, @WilliamR.Alves . Yes, this could be the reason for the issue. Unfortunately, environmental changes need to be done after the RCA, and initially, we are checking possible causes for the issue.
After narrowing down the issue, the following configuration could be the reason for this to happen:
Camunda Telemetry configuration
As per the documentation, there is a dedicated thread for this. It will check camunda.telemetry.enabled; otherwise, it will try to insert a record. In our environment, we have not configured it, and it is enabled by default. Camunda also recommends disabling this as well.
Could this be the reason?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
