[MXS-2418] Crash on transaction replay if log_info is on and session starts with no master Created: 2019-04-03 Updated: 2019-06-04 Resolved: 2019-04-03 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | readwritesplit |
| Affects Version/s: | 2.3.5 |
| Fix Version/s: | 2.3.6 |
| Type: | Bug | Priority: | Trivial |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
When configured with transaction_replay=true and log_info enabled, if a session started without a master and later on a master would become available the next start of a transaction would trigger a transaction migration. The transaction migration code unconditionally used the old master's name and if no master was available, the master reference was not valid. |
| Comments |
| Comment by markus makela [ 2019-04-03 ] |
|
Fixed by commit 260a29db3cd327740c7496ad6c8b25533b9abda6. |
| Comment by Hartmut Holzgraefe [ 2019-06-04 ] |
|
The actual commit in the 2.3 branch is 2dfd7d35ac307476847525e28f973f35cdddd538, there is no 260a29db3cd327740c7496ad6c8b25533b9abda6 in there at all ... |