Home > In-MemoryOLTP > xtp Transaction stuck

xtp Transaction stuck

 

Why the xtp transaction do not kill or rollback when a long running process is stopped?

 

A long running transaction inserting millions of records in a In-Memory OLTP Table  is stopped but the spid remains in running state, it do not kill or rollback.

 

Even you try to kill the session it do not actually kill the session. Run the Kill spid WITH STATUSONLY. It might give the below message

SPID 56: transaction rollback in progress. Estimated rollback completion: 0%. Estimated time remaining: 0 seconds.

 

We checked the sys.databases log_reuse_wait_desc column and it says waiting for xtp_checkpoint

 

image

 

We never thought the xtp transaction might keep on waiting for a checkpoint.

 

Before we manually issued the checkpoint we enabled TRACE flag 3502 & 3605 to see what happens in the background

 

DBCC TRACEON (3502, 3605, -1);

checkpoint

 

image

Categories: In-MemoryOLTP
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: