1. is backfilling/remapping so smart that it will do what ever it can? Or are there situations like a pg a. is scheduled to be moved, but can not be moved because of min_size. Now another pg b. cannot be moved because pg a. allocated osd space and the backfill ratio will be met. Yet if the order was reversed if the pg b. would be moved and pg a. would not be moved because it is stuck anyway and the backfill ratio will be met. 2. If a down host comes up again and it's osd are started. Is data still being copied, or does ceph see that checksums(?) are the same and just sets a pointer(?) back to the old location?
-----Original Message----- Sent: 09 March 2021 23:59 To: ceph-users@ceph.io Subject: [ceph-users] node down pg with backfill_wait waiting for incomplete?
I have a node down and pg's are remapping/backfilling. I have also a lot of pg's in backfill_wait.
I was wondering if there is a specific order that this is being executed. Eg I have a large'garbage' pool ec21 that is stuck. I could resolve that by changing the min size. However I rather have this not remapped, and wait for this node to be back on line.
Question is: is other remapping/backfilling waiting for this stuck to be fixed, or is backfilling/remapping so smart that it will do what ever it can?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -. F1 Outsourcing Development Sp. z o.o. Poland
t: +48 (0)12 4466 845 f: +48 (0)12 4466 843 e: marc@f1-outsourcing.eu
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io