[MCOL-954] mysqld crashing on slave replication UMs Created: 2017-10-04 Updated: 2020-08-25 Resolved: 2017-12-04 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | MariaDB Server |
| Affects Version/s: | 1.0.11 |
| Fix Version/s: | 1.0.12, 1.1.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | David Hill (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
amazon EC2 root install 3um / 5pm system |
||
| Sprint: | 2017-23, 2017-24 |
| Description |
|
Customer reproting that mysqld continually crashed on UM2/UM3, which are the slave replication nodes. Don't know if this is related or not. Thread pointer: 0x7f89e8001550 |
| Comments |
| Comment by Andrew Hutchings (Inactive) [ 2017-11-21 ] | ||
|
vtable_state was in a random state which caused an assert style crash when locking a table during a slave view create. The patch initializes vtable_state correctly. For QA: You need a 2UM (or more) setup with schema replication turned on and then do:
Before the patch it will crash the slave when it is replicated. After the patch it should create the view correctly on the slave. | ||
| Comment by Daniel Lee (Inactive) [ 2017-12-04 ] | ||
|
Builds verified: Github source 1.0.12-1 [root@localhost ~]# cat mariadb-columnstore-1.0.12-1-centos7.x86_64.bin.tar.txt Merge pull request #79 from mariadb-corporation/ /root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine Merge pull request #338 from mariadb-corporation/ 1.1.3-1 /root/columnstore/mariadb-columnstore-server Merge branch 'develop-1.1' of https://github.com/mariadb-corporation/mariadb-columnstore-server into develop-1.1 /root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine change how the os_detect is run on remote nodes Retested test scenario in the ticket, as well as more complicated scenarios. Also tested DML and queries. |