Actions
Feature #59727
openThe libradosstriper interface provides an optional parameter to avoid shared lock when reading data
% Done:
0%
Source:
Community (user)
Tags:
Backport:
Reviewed:
Description
The flow of the read operation of the current libradosstriper interface:
1. Lock (shared lock)
2. to read
3. Unlock
For the rados layer, the locking operation is a write operation. When the pg where the striper head object is located is in the deep-scrub period, if hundreds of concurrently read a libradosstriper object at the same time, a large number of slow requests will appear.
When the upper layer application can avoid read and write conflicts, the locking operation should be an optional parameter
Updated by Snow Si 12 months ago
pull request: https://github.com/ceph/ceph/pull/51443
Actions