Bug #48486
closed
readahead is incorrectly running when cache is writearound
Added by Jason Dillaman over 3 years ago.
Updated about 3 years ago.
Description
Since the writearound cache does not actually cache data in-memory, these readaheads are effectively no-ops and wasted IO cycles.
- Status changed from New to In Progress
- Assignee set to Jason Dillaman
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 38602
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #48674: octopus: readahead is incorrectly running when cache is writearound added
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF