Improve thread status visibility in PXC

Bug #1109341 reported by Vadim Tkachenko on 2013-01-29
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to
Status tracked in 5.6
Fix Released
Raghavendra D Prabhu
Fix Released
Raghavendra D Prabhu

Bug Description

For debugging purposes we want to have
- Possibility to have more thread states available that separately mention what thread is doing with regard to Galera work, rather then using the same MySQL thread states, it will help a lot in finding out what is going on. For example, when debugging locking issues in a MySQL related issue it is quite easy to see a thread that is waiting on meta-data lock and has blocked other threads. If we can have similar different Galera related thread states, then it would be very useful as most of the times we do debugging/troubleshooting offline i.e. after the lockup or stall event has passed and its imperative that we have as much information reported by MySQL that can be captured by tools such as pt-stalk.

- Possibility to have detailed Galera info similar to what is reported in InnoDB status.

- see different Galera structures and see what its doing, for example perhaps have an ability to be able to have a look at the receive queue or the send queue to see what is there, perhaps have different thread states, or probably something similar to InnoDB status.
We have added excellent diagnostic information to Percona Server, which really makes me, at least, very productive and which allows me to get insights into system to see what is wrong, for example by looking at the extended-slow-log information, or the extra tables in I_S database.

Changed in percona-xtradb-cluster:
assignee: nobody → Raghavendra D Prabhu (raghavendra-prabhu)
Changed in percona-xtradb-cluster:
milestone: none → 5.5.30-24.8
status: New → In Progress
Changed in percona-xtradb-cluster:
status: In Progress → Fix Committed
Changed in percona-xtradb-cluster:
status: Fix Committed → Fix Released

Percona now uses JIRA for bug reports so this bug report is migrated to:

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

Other bug subscribers