View Revisions: Issue #6716

All RevisionsBack to Issue
Summary 0006716: Deadlocks on Sybase due to default table locking scheme being overly restrictive
Revision 2025-02-05 02:33 by pbelov
Description SymmetricDS uses multiple threads to update internal and customer tables.
If a Sybase database server has overly restrictive locking scheme (allpages or datapages) this could result in SymmetricDS processes issuing dead-locked queries, which hurts performance (batch must be re-tried later).

Solution is to update SymmetricDS class AseDdlBuilder to create all tables with the locking scheme set to "datarows" explicitly. This will override default locking scheme set by DBA (or a lack of such setting resulting in a problematic default "allpages" scheme).
Revision 2025-02-05 02:24 by pbelov
Description SymmetricDS uses multiple threads to update internal and customer tables.
If a Sybase database server has overly optimistic locking scheme (allpages or datapages) this could result in SymmetricDS processes issuing dead-locked queries, which hurts performance (batch must be re-tried later).

Solution is to update SymmetricDS class AseDdlBuilder to create all tables with the locking scheme set to "datarows" explicitly. This will override default locking scheme set by DBA (or a lack of such setting resulting in a problematic default "allpages" scheme).