The business rule creates a ci.affected event for the task_ci associated with the task and additional such events for its parent records in accordance with the nature of script. The larger the relationship between CIs, the greater volume of event creation.
The issue is that we cannot process through those events. The sudden event creation due to the business rule prevents other events from being processed in a timely manner. This can cause severe performance degradation and uses up all the db connections leading to a potential outage.
Steps to Reproduce
- Set the business rule Affected ci notifications to active.
- Create an incident record.
- Associate a task record with it.
- In the task record add a configuration item (cmdb_ci) record to it. The CI item can have, for example, 10 parents associated with it.
- Update the task.
The issue only occurs with large CMDB relationships and with relationships that might form circular relationships.
The Affected ci notifications business rule is enabled by default in the base system. If you are not using this functionality, disable the business rule.
Alternatively, examine the CI Relationships [cmdb_rel_ci] table for circular references and remove them.
Related Problem: PRB597787