why keep and update rollback info for ReplicatedPG?

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

 



Hi, all

As I know, rollback is designed for ec-backend to rollback the partial
committed transaction like append, stash and attrs.
So why do we need to keep and update (can_rollback_to,
rollback_info_trimmed_to) every time in _write_log() for
ReplicatedBackend? Or it is related to other issues?
We may avoid frequently updating those information based on the pool types?

Regards
Ning Yao
--
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