Category
Administration
Seeing deadlock errors in Yellowfin logs
Resolved
This problem is related to seeing deadlock errors like below in your YF logs:
java.sql.SQLException: Transaction (Process ID 63) was deadlocked on lock
It's something you could get on startup or just using any area of the application.
The same problem 
This issue is something we usually see on SQL Server, when snapshot isolation is off.
To enable this, just run the commands below against your SQL instance:
ALTER DATABASE <DATABASENAME>
SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE <DATABASENAME>
SET READ_COMMITTED_SNAPSHOT ON
WITH ROLLBACK IMMEDIATE
These options are actually set on new installations of Yellowfin, but we've seen cases with extremely old installs or the settings being manually changed.
If you still experience deadlock errors after running the above, please let us know.
This issue is something we usually see on SQL Server, when snapshot isolation is off.
To enable this, just run the commands below against your SQL instance:
ALTER DATABASE <DATABASENAME>
SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE <DATABASENAME>
SET READ_COMMITTED_SNAPSHOT ON
WITH ROLLBACK IMMEDIATE
These options are actually set on new installations of Yellowfin, but we've seen cases with extremely old installs or the settings being manually changed.
If you still experience deadlock errors after running the above, please let us know.
This issue is something we usually see on SQL Server, when snapshot isolation is off.
To enable this, just run the commands below against your SQL instance:
ALTER DATABASE <DATABASENAME>
SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE <DATABASENAME>
SET READ_COMMITTED_SNAPSHOT ON
WITH ROLLBACK IMMEDIATE
These options are actually set on new installations of Yellowfin, but we've seen cases with extremely old installs or the settings being manually changed.
If you still experience deadlock errors after running the above, please let us know.
This issue is something we usually see on SQL Server, when snapshot isolation is off.
To enable this, just run the commands below against your SQL instance:
ALTER DATABASE <DATABASENAME>
SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE <DATABASENAME>
SET READ_COMMITTED_SNAPSHOT ON
WITH ROLLBACK IMMEDIATE
These options are actually set on new installations of Yellowfin, but we've seen cases with extremely old installs or the settings being manually changed.
If you still experience deadlock errors after running the above, please let us know.
Replies have been locked on this page!