[MDEV-13299] 0 rows affected on delete in galera cluster that actually deletes data Created: 2017-07-12 Updated: 2019-06-17 Resolved: 2019-06-17 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera |
| Affects Version/s: | 10.1.25 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Anders Kvist | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | galera, need_feedback | ||
| Environment: |
Seen in multiple environments - a dockerized environment is provided for verification and test |
||
| Description |
|
I know that writes on multiple galera nodes should be avoided or handled with care, but I've seen that simultanious deletes can result in "0 rows affected" even tough the delete is executed on the cluster and probably as a result of the result, the query is not written to the binary logs (setup to row based replication). It seems wrong that a result of a query can be "0 rows affected" and nothing written to binlogs when it actually deletes data - it should result in an error somehow so the application can handle it. I've created a simple docker setup with 3 nodes, a bash script to start it up and a bash script to run the query to make it fail... https://github.com/anderskvist/galera-debug |
| Comments |
| Comment by Jan Lindström (Inactive) [ 2019-05-20 ] |
|
Can you try with more recent version. Note that if you run random writes to all nodes they will produce a conflicts, this is not a bug. |