Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC

Audit mysqld.cc for thread_scheduler

Bug #1240500 reported by Raghavendra D Prabhu on 2013-10-16

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC	Status tracked in 5.6
5.5	Fix Released	Undecided	Raghavendra D Prabhu	Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC 5.5.34-23.7.6
5.6	Fix Released	Undecided	Raghavendra D Prabhu	Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC 5.6.14-25.1

Due to threadpool code, mysqld.cc need to be audited for thd->scheduler vs thread_scheduler.

Revision history for this message

Raghavendra D Prabhu (raghavendra-prabhu) wrote on 2013-10-16:

This affects only PXC, codership tree shouldn't be since threadpool is not there in that.

Revision history for this message

Raghavendra D Prabhu (raghavendra-prabhu) wrote on 2013-10-21:

thread_scheduler needs to replaced with thd->scheduler in

a) start_wsrep_THD
b) wsrep_close_thread

Revision history for this message

Raghavendra D Prabhu (raghavendra-prabhu) wrote on 2013-10-21:

Also, note that, this should affect only when threadpool is enabled with thread-handling=pool-of-threads.

Revision history for this message

Shahriyar Rzayev (rzayev-sehriyar) wrote on 2018-01-18:

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1476

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Bug watches keep track of this bug in other bug trackers.