(Please ignore the first part of the question since that can be done by a
shell command. I am interested in the second part.)

Thanks,
Arun

On Fri, Feb 26, 2016 at 1:05 PM, Arun M. Krishnakumar <[email protected]>
wrote:

> Hi Matteo,
>
> Thanks for the quick reply.
>
> The use case is mainly for testing and debugging during development.
>
> Is there a way to check the entry in the journal device (say a running
> count of pending entries yet to be written out to the entry log) ?
> Ideally I was thinking of querying the entry log itself.
>
> Thanks,
> Arun
>
> > On Feb 26, 2016, at 12:34 PM, Matteo Merli <[email protected]> wrote:
> >
> > Hi Arun,
> >
> > what is your use case for waiting until the entries are "flushed" into
> the
> > entry logs?
> >
> > Once the ledger.addEntry() operation completes, the entries are
> guaranteed
> > to have been written and fsynced on the journal device, from where they
> > will be recovered in case the bookie crashes before flushing to the entry
> > log.
> >
> > Matteo
> >
> > On Fri, Feb 26, 2016 at 12:13 PM Arun M. Krishnakumar <
> [email protected]>
> > wrote:
> >
> >> Hi,
> >>
> >> (I am new to bookkeeper, so please forgive my ignorance if there is
> >> something fundamental I'm missing).
> >>
> >> When working with bookkeeper and making entries we would like to be
> able to
> >> see entries flushed to disk and then examine them using existing shell
> >> commands (for debugging and test purposes).
> >>
> >> We typically use the "localbookie" command-line option and need to have
> a
> >> way to know if an entry written has made it correctly to bookkeeper and
> the
> >> disk.
> >>
> >> Currently the ways we are planning to do this  are:
> >> 1. To modify the configuration to set very low thresholds for flushing.
> >> 2. Create a listener thread on the localbookie which will listen to
> flush
> >> commands and forcibly do a  flush. (I know this is a hack, but just
> putting
> >> it out there)
> >>
> >> Is there a cleaner way to do this ? I think people may have wanted some
> >> similar functionality in the past.
> >>
> >> Thanks,
> >> Arun
> >>
>

Reply via email to