Possible inconsistent IO when using configured for multiple op threads
When 'rbd_op_threads' is set to a value higher than 1 (defaults to 1), it's quite possible for an aio flush op to complete before a predecessor aio write/discard starts. These ops need to be tracked at the time of submission so that flush can properly account for them. Currently, the ops only start being tracked when they start executing.
- Status changed from New to In Progress
The PR for issue #15688 has a fix for this issue -- ops are tracked in enqueued order so now a flush command will properly wait for all preceding ops.
This is only possible when enabing rbd_cache?
@Haomai: the issue could have happened with cache disabled as well since the flush wouldn't know to wait for a preceding write/discard.
- Status changed from In Progress to Resolved
Remaining issues being tracked under ticket #17379
Also available in: Atom