[MDEV-8275] Executing replace into select using multiple DB results to deadlock Created: 2015-06-06 Updated: 2020-12-07 Resolved: 2020-12-07 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera, Locking, Replication, Storage Engine - InnoDB |
| Affects Version/s: | 10.0.15 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Kuntal Chandra | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | galera, innodb, replication | ||
| Environment: |
Ubuntu 14.04 |
||
| Description |
|
Is replace insert into query using multiple database supported in galera cluster? I'm getting Deadlock message. The query works on a single server, but doesn't work in individual node behind galera cluster. Query and all details are posted here http://stackoverflow.com/questions/30094558/executing-mysql-replace-into-select-using-multiple-db-results-to-deadlock I'm not quite sure if its a bug or due to cluster-level optimistic concurrency control Galera works in this way. I'm done with a workaround but not sure if that is the most optimized solution or not. If it's not an intended behavior then please look into it. |
| Comments |
| Comment by Jan Lindström (Inactive) [ 2018-07-16 ] |
|
Hi, I would need the table data (you may obscure it if it contains sensitive data) at least as much as needed to repeat the issue. While you do it please upgrade server to more recent version and see if this issue is still repeatable. |