FTWRL and wsrep_causal_reads with 'show status'
Bug #1271177 reported by
Raghavendra D Prabhu
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership | Status tracked in 5.6 | |||||
5.5 |
New
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Undecided
|
Yan Zhang | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
High
|
Unassigned | |||
5.6 |
Fix Released
|
High
|
Unassigned |
Bug Description
When FTWRL is used on a node with wsrep_causal_
then, subsequent selects/show status can hang/fail on this node.
Cloned from https:/
Example: https:/
This is not repeatable for 5.6 for 'SHOW' commands but for select.
For 5.5, it is repeatable for 'SHOW' as well.
Regarding blocking on select and failing later with lock_wait_timeout, it needs to be seen if this is intended when the provider on that node has been paused. The behavior of apply and commit monitors with a paused provider needs to be checked.
Also note that this returns ER_LOCK_ WAIT_TIMEOUT which can be confusing since changing innodb_ lock_wait_ timeout has no effect on this behavior, it is the causal_read_timeout (default: 30s) which needs to be changed for this.