[MDEV-16543] Replicating to spider is fragile without retries Created: 2018-06-21 Updated: 2020-08-25 Resolved: 2019-04-12 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Spider |
| Affects Version/s: | 10.3 |
| Fix Version/s: | 10.4.5 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Mattias Jonsson | Assignee: | Kentoku Shiba (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Linux |
||
| Description |
|
I encountered a failure in the replication to a spider table that is not mentioned in the recommendations at https://mariadb.com/kb/en/library/spider-storage-engine-overview/#some-server-variables-to-set-when-using-spider. From 'show slave status\G':
It did work again after:
Can these issues be retried within the spider engine instead of failing in the engine and retried in the replication? (or are they failing after multiple attempts in the engine and the replication just continues to retry until it succeeds?) Also I would expect the default settings to handle this, rather than having to add configuration mentioned in the link above. |
| Comments |
| Comment by Kentoku Shiba (Inactive) [ 2019-03-05 ] |
|
I assume that it is naturally design that retrying transaction is done by SQL threads of the replication. This is like deadlock and lock wait timeout. |
| Comment by Kentoku Shiba (Inactive) [ 2019-03-05 ] |
|
Would you please review this changes? |
| Comment by Kentoku Shiba (Inactive) [ 2019-04-12 ] |
|
merged into 10.4 tree |