Deadlocks in MySQL schema (#126)

Andrzej Wójcik (Tigase) opened 4 years ago

With MySQL, we are experiencing deadlocks. As it was discussed in relation to #servers-350, most likely this is a result of "non deterministic" functions marked as deterministic and possible order of execution when user is being removed in TigPubSubRemoveService stored procedure.

Related
- Exception thrown within StoredProcedure that has transaction can cause a lock (#136) Closed

Activities

Andrzej Wójcik (Tigase) commented 4 years ago

I suppose that "deadlock" was most likely caused by TigPubSubRemoveService which concurrently tried to acquire the lock on items and then on jids while inserting procedure was creating a lock on jids and then on items table. I've adjusted order of locks that should fix this issue.

Additionally, I've replaced functions ensureJid and ensureServiceJid with stored procedures to make them more compliant with MySQL binlog.
Login to comment

Type	Bug
Priority	Normal
Assignee	Wojciech Kapcia (Tigase)
Version	tigase-server-8.2.0

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/tigase-pubsub#126