Unfortunately, parsing debug log is no-go since it doesn't print the complete command.
I've 2 approached in mind as of now 1. Modify of org.apache.zookeeper.server.LogFormatter to support "tailing". 2. Use ngrep on my local to monitor the network traffic to remote ZK host & port 2181 Will get back with what works better. - zodvik On Thu, Mar 1, 2018 at 1:22 AM, Andor Molnar <an...@cloudera.com> wrote: > Hi Zod, > > I think there's no such thing in ZooKeeper currently other than debug logs. > You might want to attach some processing engine to the debug log feed and > parse and output data which is important for you into MySQL or Redis > database. > > The downside of this approach is debug logging has significant performance > impact on the entire ensemble, but it might be acceptable for you analysis. > > Regards, > Andor > > > > On Tue, Feb 27, 2018 at 11:26 PM, Zod <zod...@gmail.com> wrote: > > > I want see all commands issued to my Zookeeper cluster, something like > > general log in MySQL or "monitor" command in Redis. How can this be done? > > > > The intent is to see how Storm uses Zookeeper (for state management & > > ack-ing) and a good way to would be to run a sample topology and see all > > the commands issued to Zookeeper by Storm. > > > > I tried enabling debug log for Zookeeper, but that is insufficient has a > > lot of noise. For example, issue a create /node prints > > > > 2018-02-27 18:05:34 ZooKeeperMain [DEBUG] Processing create > > - > > zodvik > > >
