> Yes, the reservation mechanism is rather complex and intertwined with
> the recovery state machine. There was some discussion about this
> (including the idea of backoffs) before:
Thanks!
Josh
___
ceph-users mailing list -- ceph-users@ceph.io
To unsub
Hey Josh,
Thanks for the info!
> With respect to reservations, it seems like an oversight that
> we don't reserve other shards for backfilling. We reserve all
> shards for recovery [0].
Very interesting that there is a reservation difference between
backfill and recovery.
> On the other hand, o
On 4/21/21 9:29 AM, Josh Baergen wrote:
Hey Josh,
Thanks for the info!
With respect to reservations, it seems like an oversight that
we don't reserve other shards for backfilling. We reserve all
shards for recovery [0].
Very interesting that there is a reservation difference between
backfill
Hey Josh, adding the dev list where you may get more input.
Generally I think your analysis is correct about the current behavior.
In particular if another copy of a shard is available, backfill or
recovery will read from just that copy, not the rest of the OSDs.
Otherwise, k shards must be rea
