You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by Sijie Guo <gu...@gmail.com> on 2017/10/02 01:53:58 UTC
Re: Preview of BP-14 Volatile durability ledgers Journal no-sync
Can you organize the preview in multiple changes that would eventually be
sent out as prs? It would be easier to review.
On Sep 29, 2017 4:41 AM, "Enrico Olivelli" <eo...@gmail.com> wrote:
> Hi BookKeepers,
> I would like to share the prototype for BP-14
>
> https://cwiki.apache.org/confluence/display/BOOKKEEPER/
> BP-14+Relax+durability
>
> I sent a WIP Pull Request
> https://github.com/apache/bookkeeper/pull/529
>
>
> Please note that this work depends on BP-15 (PR #510) because we are going
> to use the new CreateLedger API.
> Temporary I have added a lot of overloaded versions of
> createLedger/createLedgerAdv but using the new API these new methods will
> not be added.
>
> I will try to split the patch in smaller tasks but I will appreciate if you
> have some cycle to start looking at how it will look like.
>
> Most notable changes:
> - introducing a LedgerType in ledger metadata
> - changes to wire protocol: optional LedgerType in AddRequest, changes in
> AddResponse, new protocol messages for the Sync API
> - changes to LederHandle#sendAddSuccessCallbacks (this is the main change
> to the LAC Protocol on the client-side)
> - for volatile durability changes LastAddConfirmed will advance only in
> presence of an explicit "sync"
> - introduction of SyncCounter on Journal to keep track of which entries
> have been really persisted durably
> - new Sync API (this will be subject to change, it will follow the "new
> style" of BP-15 APIs)
> - on close() a sync will not be performed automatically on volatile
> durability ledgers
>
>
> Cheers
> Enrico
>
Re: Preview of BP-14 Volatile durability ledgers Journal no-sync
Posted by Enrico Olivelli <eo...@gmail.com>.
This is the first patch, this patch introduces changes to the wire protocol
and to ledger metadata stored on ZK
https://github.com/apache/bookkeeper/pull/531
Enrico
2017-10-02 11:04 GMT+02:00 Enrico Olivelli - Diennea <
enrico.olivelli@diennea.com>:
> Il giorno dom, 01/10/2017 alle 18.53 -0700, Sijie Guo ha scritto:
>
> Can you organize the preview in multiple changes that would eventually be
> sent out as prs? It would be easier to review.
>
>
> You are right, I will along this week
> I will try to follow your way of pushing the changes for the long pool
> reads, a set of chained PRs
>
> -- Enrico
>
>
>
> On Sep 29, 2017 4:41 AM, "Enrico Olivelli" <eolivelli@gmail.com<mailto:eo
> livelli@gmail.com>> wrote:
>
>
>
> Hi BookKeepers,
> I would like to share the prototype for BP-14
>
> https://cwiki.apache.org/confluence/display/BOOKKEEPER/
> BP-14+Relax+durability
>
> I sent a WIP Pull Request
> https://github.com/apache/bookkeeper/pull/529
>
>
> Please note that this work depends on BP-15 (PR #510) because we are going
> to use the new CreateLedger API.
> Temporary I have added a lot of overloaded versions of
> createLedger/createLedgerAdv but using the new API these new methods will
> not be added.
>
> I will try to split the patch in smaller tasks but I will appreciate if you
> have some cycle to start looking at how it will look like.
>
> Most notable changes:
> - introducing a LedgerType in ledger metadata
> - changes to wire protocol: optional LedgerType in AddRequest, changes in
> AddResponse, new protocol messages for the Sync API
> - changes to LederHandle#sendAddSuccessCallbacks (this is the main change
> to the LAC Protocol on the client-side)
> - for volatile durability changes LastAddConfirmed will advance only in
> presence of an explicit "sync"
> - introduction of SyncCounter on Journal to keep track of which entries
> have been really persisted durably
> - new Sync API (this will be subject to change, it will follow the "new
> style" of BP-15 APIs)
> - on close() a sync will not be performed automatically on volatile
> durability ledgers
>
>
> Cheers
> Enrico
>
>
>
> --
>
> Enrico Olivelli Software Development Manager @Diennea Tel.: (+39) 0546
> 066100 - Int. 925 Viale G.Marconi 30/14 - 48018 Faenza (RA) MagNews -
> E-mail Marketing Solutions http://www.magnews.it Diennea - Digital
> Marketing Solutions http://www.diennea.com
>
> ________________________________
>
> Iscriviti alla nostra newsletter per rimanere aggiornato su digital ed
> email marketing! http://www.magnews.it/newsletter/
>
> The information in this email is confidential and may be legally
> privileged. If you are not the intended recipient please notify the sender
> immediately and destroy this email. Any unauthorized, direct or indirect,
> disclosure, copying, storage, distribution or other use is strictly
> forbidden.
>
Re: Preview of BP-14 Volatile durability ledgers Journal no-sync
Posted by Enrico Olivelli - Diennea <en...@diennea.com>.
Il giorno dom, 01/10/2017 alle 18.53 -0700, Sijie Guo ha scritto:
Can you organize the preview in multiple changes that would eventually be
sent out as prs? It would be easier to review.
You are right, I will along this week
I will try to follow your way of pushing the changes for the long pool reads, a set of chained PRs
-- Enrico
On Sep 29, 2017 4:41 AM, "Enrico Olivelli" <eo...@gmail.com>> wrote:
Hi BookKeepers,
I would like to share the prototype for BP-14
https://cwiki.apache.org/confluence/display/BOOKKEEPER/
BP-14+Relax+durability
I sent a WIP Pull Request
https://github.com/apache/bookkeeper/pull/529
Please note that this work depends on BP-15 (PR #510) because we are going
to use the new CreateLedger API.
Temporary I have added a lot of overloaded versions of
createLedger/createLedgerAdv but using the new API these new methods will
not be added.
I will try to split the patch in smaller tasks but I will appreciate if you
have some cycle to start looking at how it will look like.
Most notable changes:
- introducing a LedgerType in ledger metadata
- changes to wire protocol: optional LedgerType in AddRequest, changes in
AddResponse, new protocol messages for the Sync API
- changes to LederHandle#sendAddSuccessCallbacks (this is the main change
to the LAC Protocol on the client-side)
- for volatile durability changes LastAddConfirmed will advance only in
presence of an explicit "sync"
- introduction of SyncCounter on Journal to keep track of which entries
have been really persisted durably
- new Sync API (this will be subject to change, it will follow the "new
style" of BP-15 APIs)
- on close() a sync will not be performed automatically on volatile
durability ledgers
Cheers
Enrico
--
Enrico Olivelli Software Development Manager @Diennea Tel.: (+39) 0546 066100 - Int. 925 Viale G.Marconi 30/14 - 48018 Faenza (RA) MagNews - E-mail Marketing Solutions http://www.magnews.it Diennea - Digital Marketing Solutions http://www.diennea.com
________________________________
Iscriviti alla nostra newsletter per rimanere aggiornato su digital ed email marketing! http://www.magnews.it/newsletter/
The information in this email is confidential and may be legally privileged. If you are not the intended recipient please notify the sender immediately and destroy this email. Any unauthorized, direct or indirect, disclosure, copying, storage, distribution or other use is strictly forbidden.