We've added an additional command to "bookkeeper shell" tools, to dump the entries payloads for ledgers (closed or not). We'll submit a pull-req soon.
On Thu, Mar 3, 2016 at 3:29 PM Venkateswara Rao Jujjuri <[email protected]> wrote: > Matteo do you mean you have an admin port patch? Can you please share it?? > What kind of operations can be performed on that port?? > > Thanks, > JV > > On Tue, Mar 1, 2016 at 11:56 PM, Matteo Merli <[email protected] > > > wrote: > > > Sijie, > > we have a similar tool in our internal branch, readledger to dump the > > content of a (possibly still open) ledger. We'll submit for PR. > > > > Matteo > > > > On Tuesday, March 1, 2016 10:19 AM, Sijie Guo <[email protected]> > > wrote: > > > > > > Yup. it would be nice if you could abstract this into a shell command, > > like > > 'tail <ledger-id>', that would be useful. > > > > On Mon, Feb 29, 2016 at 11:31 AM, Enrico Olivelli <[email protected]> > > wrote: > > > > > Hi Arun, > > > IMHO if you just need to see the content of a ledger you can write a > > simple > > > client which opens a given ledger using no-recovery mode and dump the > > > contents to disk to another file or just to stdout > > > > > > Enrico > > > > > > Il Lun 29 Feb 2016 19:34 Arun M. Krishnakumar <[email protected]> ha > > > scritto: > > > > > > > Hi Sijie, > > > > > > > > Yes, that's correct. The work-item is about building an admin command > > to > > > > force the flush and I was looking for any option or workaround to do > > the > > > > job. > > > > > > > > As we understand it, there doesn't seem to be a nice way to > communicate > > > > with the bookies for such OOB (out of band) requests. So one of the > > > options > > > > is to have a separate communication channel from the shell to the > > bookie. > > > > This would enable other interesting commands such as querying the > exact > > > > states of various caches, getting some statistical numbers etc. > > > > > > > > Do you have any other requirements that would fall into this general > > > > operational category ? If so, and if the approach isn't too bad, we > > could > > > > work on a clean channel and protocol that could be used for such > > > > communications. > > > > > > > > Thanks, > > > > Arun > > > > > > > > On Mon, Feb 29, 2016 at 9:45 AM, Sijie Guo <[email protected]> wrote: > > > > > > > > > We don't have the mechanism to trigger/force a flush by the command > > > right > > > > > now. > > > > > > > > > > Arun: > > > > > > > > > > As my understanding on your question, you want to admin command > that > > > you > > > > > could issue to trigger the flush, right? > > > > > > > > > > - Sijie > > > > > > > > > > On Fri, Feb 26, 2016 at 10:33 PM, Venkateswara Rao Jujjuri < > > > > > [email protected]> wrote: > > > > > > > > > > > Also do we have a way to flush to ledger on disk? Some of the > > bookie > > > > > shell > > > > > > commands will fail if there is no disk entry for journals. > > > > > > > > > > > > Thanks, > > > > > > JV > > > > > > > > > > > > On Sat, Feb 27, 2016 at 5:29 AM, Arun M. Krishnakumar < > > > > > [email protected]> > > > > > > wrote: > > > > > > > > > > > > > (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 > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Jvrao > > > > > > --- > > > > > > First they ignore you, then they laugh at you, then they fight > you, > > > > then > > > > > > you win. - Mahatma Gandhi > > > > > > > > > > > > > > > > > > -- > > > > > > > > > -- Enrico Olivelli > > > > > > > > > > > > > > > -- > Jvrao > --- > First they ignore you, then they laugh at you, then they fight you, then > you win. - Mahatma Gandhi >
