Re: [crimson] replicated write as a phase in PGPipeline

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

 



sorry for the double post. forwarding to the correct list.

On Fri, Jul 12, 2019 at 9:16 PM kefu chai <tchaikov@xxxxxxxxx> wrote:
>
> hi Sam,
>
> as you know, i am working on replicated write. and, i think we need to
> make it an optional phase in ClientRequest::PGPipeline, but i am not
> quite sure about how we should represent it as a blocking step using
> dump_detail()
>
> currently, my plan is to add a Blocker for wrapping 1 * local_txn + m
> * replicated_txn. and print them as
> - a tid,
> - a local return code
> - an array of {peer:pg_shard_t, last_complete_on_disk:eversion}
>
> does this make sense to you?
>
> --
> Regards
> Kefu Chai



-- 
Regards
Kefu Chai
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx



[Index of Archives]     [CEPH Users]     [Ceph Devel]     [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