Percona XtraDB Cluster - HA scalable solution for MySQL

attempt to kill slave thread can cause server hanging

Reported by Seppo Jaakola on 2012-12-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Status tracked in 5.6
5.5
Low
Seppo Jaakola
5.6
Low
Seppo Jaakola
Percona XtraDB Cluster
Status tracked in Trunk
5.6
Undecided
Unassigned
Trunk
Undecided
Unassigned

Bug Description

High priority threads (slave threads, replaying threads, total order isolation threads) are not protected from kill signal and attempt to kill high priority thread can cause server to hang. One such a scenario is reported in MariaDB project: https://mariadb.atlassian.net/browse/MDEV-3924

As a fix, high priority threads should be protected from kill.

Changed in codership-mysql:
importance: Undecided → Low
assignee: nobody → Seppo Jaakola (seppo-jaakola)
milestone: none → 5.5.28-23.8
Changed in codership-mysql:
status: New → In Progress
milestone: 5.5.30-24.8 → 5.5.31-23.7.4
Seppo Jaakola (seppo-jaakola) wrote :

The fix will prevent kill command for appliers, aborter thread, replaying local connections or local connections in commit state
Fix pushed in revision: http://bazaar.launchpad.net/~codership/codership-mysql/5.5-23/revision/3870

Changed in codership-mysql:
status: In Progress → Fix Committed
Changed in percona-xtradb-cluster:
milestone: none → 5.5.31-24.8
Changed in percona-xtradb-cluster:
status: New → Fix Committed
tags: added: codership
Changed in percona-xtradb-cluster:
status: Fix Committed → Fix Released
Changed in codership-mysql:
status: Fix Committed → Fix Released

The fix of this issue is not present in 5.6 tree, hence adding 5.6 component.

@Codership,

This is required for 5.6 too right?

Seppo Jaakola (seppo-jaakola) wrote :

Added 5.6 branch in work queue, merge will appear within short

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers