Feature #14034
Updated by Samuel Just about 8 years ago
EC overwrites require two new concepts: 1) The log must have an applied_up_to line. All log entries before that point have been applied, all entries after that point have not. Each log entry needs to be able to be applied by adding operations to a transaction. There is a similarity between this and the machinery for trimming rollback info currently present in PGLog. I suggest that we subsume that mechanism by cleaning up the rollback object for a delete when the log entry is applied. 2) Each log entry needs to include information which records which shards (shard/crush position, not osd) actually participated. We may want to play with the encoding a bit here since all replicated pool entries and many ec pool entries will have involved all shards. 2) Add logic and unit tests for PGLog.h/cc to test this new code until the rest of the pieces are in place.