Re: PG recovery reservation state chart

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> This all looks right to me.  I only have one concern: if, at some future 
> point, we decide it's necessary or worthwhile to avoid non-backfill 
> recovery due to targets begin full, does this approach preclude an elegant 
> solution?

I believe this encourages an elegant solution:

We add a new state if a remote reservation is rejected:

   WaitRemoteRecoveryReserved -> SleepALittle -> LocalReserving
  
In the new state we drop the remote reservations we acquired and wait
until a timer goes off before transitioning back into LocalReserving.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux