Re: [ceph-users] why not add (offset,len) to pglog

Thank you for your reply. I am looking formard to Sage's opinion too @sage. Also I'll keep on with the BlueStore and Kstore's progress. Regards 2015-12-25 14:48 GMT+08:00 Ning Yao : > Hi, Dong Wu, > > 1. As I currently work for other things, this proposal is abandon for > a

Re: [ceph-users] why not add (offset,len) to pglog

On Fri, 25 Dec 2015, Ning Yao wrote: > Hi, Dong Wu, > > 1. As I currently work for other things, this proposal is abandon for > a long time > 2. This is a complicated task as we need to consider a lots such as > (not just for writeOp, as well as truncate, delete) and also need to > consider the

Re: [ceph-users] why not add (offset,len) to pglog

Hi, Dong Wu, 1. As I currently work for other things, this proposal is abandon for a long time 2. This is a complicated task as we need to consider a lots such as (not just for writeOp, as well as truncate, delete) and also need to consider the different affects for different backends(Replicated,

Re: [ceph-users] why not add (offset,len) to pglog

Thanks, from this pull request I learned that this issue is not completed, is there any new progress of this issue? 2015-12-25 12:30 GMT+08:00 Xinze Chi (信泽) : > Yeah, This is good idea for recovery, but not for backfill. > @YaoNing have pull a request about this >

Re: [ceph-users] why not add (offset,len) to pglog

Yeah, This is good idea for recovery, but not for backfill. @YaoNing have pull a request about this https://github.com/ceph/ceph/pull/3837 this year. 2015-12-25 11:16 GMT+08:00 Dong Wu : > Hi, > I have doubt about pglog, the pglog contains (op,object,version) etc. > when