This counter counts the messages exchanged with other cluster members specifically to support cross-node deadlock detection. A rising count here reflects growing cluster-wide lock manager overhead dedicated to checking for deadlocks, distinct from the ordinary lock and unlock traffic itself. For example, an application whose locks span resources mastered on several different cluster nodes would generate more cross-node deadlock-detection messages than one confined to a single node.