Jira Charting Plugin may cause a deadlock in the database when multiple nodes attempt to perform CF updates
The issue manifests when the following scenario occurs:
An issue operation is performed to an issue on Node A
Node A replicates the index operation to Node B and Node C
Node B and Node C attempts to reindex the issue simultaneously
Reindexing an issue when the Jira Charting Plugin is installed will reindex the Time in Status Custom Field, causing it to recalculate, so that the recalculated value may be written into the node's index. This recalculation begins with a deletion to the custom field's value in the database.
The same delete statement is made to the database's customfieldvalue table from multiple nodes, resulting in a deadlock
NodeReindexServiceThread thread shows a stack trace similar to the following: