[MDEV-23929] innodb_flush_neighbors is not being ignored for system tablespace on SSD Created: 2020-10-09 Updated: 2022-02-21 Resolved: 2022-02-21 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.4 |
| Fix Version/s: | 10.5.7 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Marko Mäkelä |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | performance | ||
| Environment: |
Linux |
||
| Issue Links: |
|
||||||||||||
| Description |
|
It turns out that fil_system.sys_space->rotational() will wrongly hold at least on 10.5 where I tested it. Maybe we only ever invoke fil_node_t::find_metadata() on .ibd files, but never on the special tablespaces (system tablespace, temporary tablespace, undo tablespaces). Note: /dev/shm will be reported to be rotational. |
| Comments |
| Comment by Marko Mäkelä [ 2020-10-15 ] |
|
The fil_space_t refactoring in |
| Comment by Marko Mäkelä [ 2022-02-21 ] |
|
I don’t think that it makes much sense to fix this bug in 10.4, because affected users can upgrade to 10.5 or later, or simply use the setting innodb_flush_neighbors=OFF. |