[MDEV-10518] Large wsrep_gtid_domain_id may break IST Created: 2016-08-08 Updated: 2016-08-25 Resolved: 2016-08-25 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera SST |
| Affects Version/s: | 10.1.16 |
| Fix Version/s: | 10.1.17 |
| Type: | Bug | Priority: | Major |
| Reporter: | Andrew Garner | Assignee: | Nirbhay Choubey (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
A test environment was generating server_id / wsrep_gtid_domain_id based on certain unsigned 32-bit hash values. This sometimes resulted in a large unsigned value:
When restarting a node and IST was initiated, the wsrep-sst-method=xtrabackup-v2 script was started with a negative gtid-domain-id as seen in the donor's logs:
And this resulted in a failure on the joiner:
As a workaround, the wsrep_gtid_domain_id was clamped to range of a signed 32-bit integer and this problem was avoided. However, I think this should probably work. |
| Comments |
| Comment by Andrew Garner [ 2016-08-08 ] |
|
I see I was a bit off in my analysis - clamping to a positive signed 32-bit integer isn't sufficient - I just got lucky when I adjusted the value. I see where this error stems from and the value of wsrep-gtid-domain-id is restricted to the range of 16-bit integer here: So a workaround requires keeping this value within a bit smaller range than I originally suggested. |
| Comment by Nirbhay Choubey (Inactive) [ 2016-08-23 ] |
|
andrew.garner Thanks for pointing it out! |
| Comment by Nirbhay Choubey (Inactive) [ 2016-08-23 ] |
|
http://lists.askmonty.org/pipermail/commits/2016-August/009684.html |