我们在生产环境中看到了很多这样的查询内并行线程死锁(SQL Server 2012 SP2 - 是的......我知道......),但是当查看通过扩展事件捕获的死锁 XML 时,受害者列表为空。
<victim-list />
死锁似乎在 4 个线程之间,两个与.WaitType="e_waitPipeNewRow"
和两个与WaitType="e_waitPipeGetRow"
.
<resource-list>
<exchangeEvent id="Pipe13904cb620" WaitType="e_waitPipeNewRow" nodeId="19">
<owner-list>
<owner id="process4649868" />
</owner-list>
<waiter-list>
<waiter id="process40eb498" />
</waiter-list>
</exchangeEvent>
<exchangeEvent id="Pipe30670d480" WaitType="e_waitPipeNewRow" nodeId="21">
<owner-list>
<owner id="process368ecf8" />
</owner-list>
<waiter-list>
<waiter id="process46a0cf8" />
</waiter-list>
</exchangeEvent>
<exchangeEvent id="Pipe13904cb4e0" WaitType="e_waitPipeGetRow" nodeId="19">
<owner-list>
<owner id="process40eb498" />
</owner-list>
<waiter-list>
<waiter id="process368ecf8" />
</waiter-list>
</exchangeEvent>
<exchangeEvent id="Pipe4a106e060" WaitType="e_waitPipeGetRow" nodeId="21">
<owner-list>
<owner id="process46a0cf8" />
</owner-list>
<waiter-list>
<waiter id="process4649868" />
</waiter-list>
</exchangeEvent>
</resource-list>
所以:
- 受害者名单为空
- 运行查询的应用程序不会出错并完成查询
- 就我们所见,没有明显的问题,只是图被捕获了
因此,除了噪音还有什么需要担心的吗?