You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@bookkeeper.apache.org by Maurício Santiago de Castro <ma...@hotmail.com> on 2015/11/25 13:09:17 UTC
hint about ledger removal
A question / suggestion request for the experts:
I have to keep ledgers until a certain condition applies, where this
condition needs to be updated.
Considering this update can come from different bookkeeper clients, is
it a good idea to create a path in ZK and keep the ledgers list there
together with the condition and mutex lock it (using Curator's recipe)
to change it?
Does it make sense?
Is there any other Bookkeeper "native" way to do something like this? or
another more sane (simpler?) idea?
Thanks.
Regards.
--
Maurício Santiago de Castro
mauriciosantiagodecastro
mauricioscastro@hotmail.com <ma...@hotmail.com>
<http://br.linkedin.com/pub/mauricio-castro/17/275/a5b>
<http://www.delicious.com/mscastro>
<http://twitter.com/#%21/mauricioscastro>
mauriciosantiagodecastro@facebook
<http://facebook.com/mauriciosantiagodecastro>
<https://mscastro.startssl.com/>
Re: hint about ledger removal
Posted by Mauricio Castro <ma...@hotmail.com>.
sure, thanks a lot.
Sent from my Sony Xperia™ smartphone
---- Sijie Guo wrote ----
for my understanding, this seems to be a coordination case, you are
coordinating the bookkeeper clients to delete ledgers after meeting a
certain condition.
zookeeper is a good candidate to do such coordination than bookkeeper. as
bookkeeper is more focus on replication and consistency on replicated log.
does that make sense?
- Sijie
On Wed, Nov 25, 2015 at 4:09 AM, Maurício Santiago de Castro <
mauricioscastro@hotmail.com> wrote:
> A question / suggestion request for the experts:
>
> I have to keep ledgers until a certain condition applies, where this
> condition needs to be updated.
>
> Considering this update can come from different bookkeeper clients, is it
> a good idea to create a path in ZK and keep the ledgers list there together
> with the condition and mutex lock it (using Curator's recipe) to change it?
>
> Does it make sense?
>
> Is there any other Bookkeeper "native" way to do something like this? or
> another more sane (simpler?) idea?
>
> Thanks.
>
> Regards.
>
> --
>
> Maurício Santiago de Castro
>
> mauriciosantiagodecastro
>
> [image: mauricioscastro@hotmail.com] <ma...@hotmail.com>
> <http://br.linkedin.com/pub/mauricio-castro/17/275/a5b>
> <http://www.delicious.com/mscastro>
> <http://twitter.com/#%21/mauricioscastro> [image:
> mauriciosantiagodecastro@facebook]
> <http://facebook.com/mauriciosantiagodecastro>
> <https://mscastro.startssl.com/>
>
Re: hint about ledger removal
Posted by Sijie Guo <si...@apache.org>.
for my understanding, this seems to be a coordination case, you are
coordinating the bookkeeper clients to delete ledgers after meeting a
certain condition.
zookeeper is a good candidate to do such coordination than bookkeeper. as
bookkeeper is more focus on replication and consistency on replicated log.
does that make sense?
- Sijie
On Wed, Nov 25, 2015 at 4:09 AM, Maurício Santiago de Castro <
mauricioscastro@hotmail.com> wrote:
> A question / suggestion request for the experts:
>
> I have to keep ledgers until a certain condition applies, where this
> condition needs to be updated.
>
> Considering this update can come from different bookkeeper clients, is it
> a good idea to create a path in ZK and keep the ledgers list there together
> with the condition and mutex lock it (using Curator's recipe) to change it?
>
> Does it make sense?
>
> Is there any other Bookkeeper "native" way to do something like this? or
> another more sane (simpler?) idea?
>
> Thanks.
>
> Regards.
>
> --
>
> Maurício Santiago de Castro
>
> mauriciosantiagodecastro
>
> [image: mauricioscastro@hotmail.com] <ma...@hotmail.com>
> <http://br.linkedin.com/pub/mauricio-castro/17/275/a5b>
> <http://www.delicious.com/mscastro>
> <http://twitter.com/#%21/mauricioscastro> [image:
> mauriciosantiagodecastro@facebook]
> <http://facebook.com/mauriciosantiagodecastro>
> <https://mscastro.startssl.com/>
>