[MDEV-9915] service stop with parallel replication failing Created: 2016-04-13 Updated: 2016-05-28 Resolved: 2016-05-24 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Platform RedHat, Replication |
| Affects Version/s: | 10.1.12 |
| Fix Version/s: | 10.1.13 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Diego Hellas | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Environment: |
CentOS 7 |
||
| Attachments: |
|
| Description |
|
I'm using a MariaDB with replication parallel. |
| Comments |
| Comment by Daniel Black [ 2016-04-15 ] | |
|
How are you stopping the service? Can you use gdb to grab a backtrace while it is in its zombie status?
What also are the last messages written to the error log? If you do a STOP SLAVE SQL_THREAD; does this complete ok? What are your replication settings? What version is the master? Are you replicating in gtid mode? Are you using any aggressive mode replication? | |
| Comment by Kristian Nielsen [ 2016-04-15 ] | |
|
It sounds like it could be the same problem as Maybe you can test if the patch for http://lists.askmonty.org/pipermail/commits/2016-March/009069.html | |
| Comment by Diego Hellas [ 2016-04-18 ] | |
| Comment by Elena Stepanova [ 2016-05-18 ] | |
|
diegohellas, have you had a chance to upgrade to 10.1.13 as Kristian suggested above? If you had, have you experienced the problem since then? | |
| Comment by Diego Hellas [ 2016-05-24 ] | |
|
@Elena, in MariaDB 10.1.13 works. | |
| Comment by Kristian Nielsen [ 2016-05-24 ] | |
|
Ok, closing then as duplicate of
|