WAIT_XTP_TASK_SHUTDOWN is recorded while a thread waits for an In-Memory OLTP thread to complete and shut down. XTP runs its own background threads (checkpoint workers, garbage collection helpers), and orderly teardown, at database offline, instance shutdown, or internal reorganisation, means waiting for them to finish.
Lifecycle machinery, active at endings.
Is It a Problem?
No; it has not been a contention point, and it accumulates only around shutdown-shaped events for XTP components. It belongs on the benign filter list with the rest of the family.
The only conceivable interest is forensic: a database offline or instance shutdown that drags while XTP is involved might show time here, in which case whatever the XTP thread was finishing (a checkpoint close, typically) was the actual clock.
Common Causes
- Database offline/instance shutdown tearing down XTP background threads.
- Internal XTP thread lifecycle events on databases with memory-optimized objects.
What To Do
- Filter it out of wait analysis.
- For slow shutdowns involving XTP databases, read the error log’s shutdown sequence; the waiting is downstream of whatever XTP work had to finish.
How To See It
Rank waits with Get-WaitStatistics, where it is filtered as XTP lifecycle noise.
Part of the SQL Server Wait Types Library.
Related deep dive: WRITELOG Wait Type.
Leave a Reply