Skip to main content
Solved

Execution stuck on Ingest Transfer


Pontus Olausson
Contributor
Forum|alt.badge.img

TimeXtender Data Integration 6848.1
Ingest Service 6848.1

 

We are experiencing issues with ingest transfer (from ingest instance to prepare instance) in our warehouse, where executions that normally take a couple of minutes get stuck on Ingest Transfer task for hours at a time. This mostly occurs when the table we execute in the prepare instance has mappings to a data source that at the same time executes in the ingest instance (even though that specific table does not execute at that time).

Both the Ingest instance and the Prepare instance use SQL Server storage, hosted on the same VM as the data integration service and the ingest service. The Prepare instance uses ADO.net transfer.

 

There are no suspended queries on the SQL Server while the execution is stuck. I’ve also checked perfmon for CPU performance: the CPU averages 80 % and the processor queue length averages 6 (ranges from 0 to 16) during executions that get stuck. Our VM has 4 vCores.

The SQL Server has 32 GB maximum server memory, and ExecutionEngine_x64.exe also uses ~32 GB during executions. Our VM has dynamic RAM, I’m unsure of the max.

Our SQL databases are all stored on the same disk, which is currently almost at capacity. However, average read and write times in perfmon seem to be low.

 

I’m thankful for any help in troubleshooting.

 

Best,

Pontus

 

Best answer by Christian Hauggaard

Hi ​@Pontus Olausson 

Please try to scale up the VM or try to place the SQL server on a different VM from the application VM, you can also separate the application VM and the Ingest VM (where the ingest service is running). By separating these, they will not compete for resources on the same VM.

View original
Did this topic help you find an answer to your question?

3 replies

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi ​@Pontus Olausson 

Please try to scale up the VM or try to place the SQL server on a different VM from the application VM, you can also separate the application VM and the Ingest VM (where the ingest service is running). By separating these, they will not compete for resources on the same VM.


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi ​@Pontus Olausson did you get a chance to try the above?


Pontus Olausson
Contributor
Forum|alt.badge.img

Hi ​@Christian Hauggaard 

We are in the process of separating the SQL Server from the application VM. I’ll provide an update on the effect once implemented and tested.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings