[MDEV-7100] InnoDB error monitor might unnecessary wait log_sys mutex Created: 2014-11-13 Updated: 2014-11-13 Resolved: 2014-11-13 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB, Storage Engine - XtraDB |
| Affects Version/s: | 5.5.40, 10.0.14 |
| Fix Version/s: | 5.5.41, 10.0.15 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Jan Lindström (Inactive) | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | innodb, xtradb | ||
| Description |
|
InnoDB error monitor is responsible to call every second This is not possible if error monitor itself is on mutex/semaphore wait. We should avoid all unnecessary mutex/semaphore waits on error monitor. Currently error monitor calls function buf_flush_stat_update() that calls log_get_lsn() function and there we will try to get log_sys mutex. Better, solution for error monitor is that in buf_flush_stat_update() we will try to get lsn with mutex_nowait() and if we did not get mutex do not update the stats. |
| Comments |
| Comment by Jan Lindström (Inactive) [ 2014-11-13 ] |
|
revno: 4347 Analysis: InnoDB error monitor is responsible to call every second Fix: Use log_get_lsn_nowait() function on buf_flush_stat_update() |
| Comment by Jan Lindström (Inactive) [ 2014-11-13 ] |
|
revno: 4481 Analysis: InnoDB error monitor is responsible to call every second Fix: Use log_get_lsn_nowait() function on buf_flush_stat_update() |