Hi Robert
I have kept Number of Streams and update threads both are 1 only , but still its giving the deadlock, after next run the job will execute without any error message. Its only happenings in the weekends, where other masking jobs also run .
Lets say Job 1( 2 rulesets) runs every day including weekends, and job 2(17 Rulesets takes longer time) runs only sunday. When Job 2 runs, the Job 1 runs slow and it fails with deadlock error and after rerun the Job 1 it will be successful.
------------------------------
Karteek Muthyala
Information Security Engineer
Wells Fargo Bank, N.A.
------------------------------
Original Message:
Sent: 05-29-2023 11:12:17 AM
From: Robert Henning
Subject: Masking Job Deadlock
Hi Karteek,
Thanks for reaching out. In your masking job, could you share the number of streams and update threads you are using? If the integer for threads is higher than 1, please update it to 1 and try running that job again.
Thanks!
------------------------------
Robert Henning
Principal Solutions Engineer
Delphix
Original Message:
Sent: 05-29-2023 09:17:34 AM
From: Karteek Muthyala
Subject: Masking Job Deadlock
Hi Team
Frequently am observing the below error message in one of the Masking job, and its run on gold VDB, and there are nothing is running in SQL server..
2023/05/29 06:19:20 - Table input.0 - Couldn't get row from result set
2023/05/29 06:19:20 - Table input.0 - Transaction (Process ID 92) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.ransaction (Process ID 110) was deadlocked on lock resources with another process a.
| Event | Cause | Description |
|---|
| JOB_ABORTED | UNHANDLED_EXCEPTION | Exception:2023/05/29 04:55:27 - Table input.0 - ERROR (version 7.1.0.0-12, build 1 from 2017-05-16 17.18.02 by buildguy) : org.pentaho.di.core.exception.KettleDatabaseException: 2023/05/29 04:55:27 - Table input.0 - Couldn't get row from result set 2023/05/29 04:55:27 - Table input.0 - Transaction (Process ID 110) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. 2023/05/29 04:55:27 - Table input.0 - |
| JOB_ABORTED | UNHANDLED_EXCEPTION | Exception:org.pentaho.di.core.exception.KettleDatabaseException: Couldn't get row from result set Transaction (Process ID 110) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
|
------------------------------
Karteek Muthyala
Information Security Engineer
Wells Fargo Bank, N.A.
------------------------------