Gain of having code in contrib folder is that people would know about a tool. Most of the ZooKeeper users are not subscribed to this mailing list but everyone has looked into contrib folder to find useful tools. However, I agree that contrib is not a good place for development because committers would need to check in code. Maybe it would be good idea to check in only releases while development is done in different repository.
Starting incubator project is great idea if I am able to get enough interest. I'm not really sure how to spread the word about the project. I'm pretty sure that this tool can be very useful in some cases. For example when something breaks down during tests or in production environment this tool provides fast way to reconstruct events. API can be used to implement sanity check monitor that monitors interaction between components without affecting ZooKeeper service. What do you thing about that use case or using it in tests in general? Timeline feature is a pretty good idea. My next planned steps are to write this tool in Swing with interface similar to ZooInspector (or maybe extend ZooInspector) and release on Github so people could try it without having to compile first. On 17 September 2014 13:26, Flavio Junqueira <[email protected]> wrote: > Btw, I forgot to mention that I also like the tool. One of the potential > features here I see is a slide bar that allows the developer to observe the > state of the tree at different points in time. We could go forward and > backward at will. > > -Flavio > > > On Wednesday, September 17, 2014 12:09 PM, Flavio Junqueira > <[email protected]> wrote: > > > > > > > >I wouldn't mind having it in contrib. However, I haven't had any great > experience with contrib. It seems to be a dead end for the projects that go > there. Also, you'd need committers to check in your code, so it isn't clear > how much you actually gain by having your code there. > > > >One option is that you start interacting with the community here and try > to get folks to help you out with the development of the tool. If you're > able to get enough interest, then perhaps you could start an incubator > project. > > > >How does it sound? > > > >-Flavio > > > > > > > >On Wednesday, September 17, 2014 11:43 AM, Alen Čaljkušić < > [email protected]> wrote: > > > > > >> > >> > >>Thanks > >> > >>Do you think this could be included in ZooKeeper as contrib? > >> > >> > >>On 17 September 2014 06:48, Patrick Hunt <[email protected]> wrote: > >> > >>> Cool idea. > >>> > >>> Patrick > >>> > >>> On Sat, Sep 13, 2014 at 7:19 AM, Alen Čaljkušić > >>> <[email protected]> wrote: > >>> > Hello ZooKeeper community, > >>> > > >>> > I would like to present you a tool I have been working on. It is > called > >>> > zklogtool. > >>> > > >>> > Zklogtool is a ZooKeeper transactions and data tree monitoring tool. > It > >>> > works by analyzing transaction logs in real time. It can reconstruct > >>> > ZooKeepers data tree at any particular point in time. That works by > >>> loading > >>> > data tree from snapshot file and applying transactions to it. > >>> > > >>> > Zklogtool project consists of zklogtool library, console application > and > >>> > web application. > >>> > > >>> > Possible use cases are: > >>> > > >>> > - Learning ZooKeeper > >>> > > >>> > - Developer tool > >>> > > >>> > - Troubleshooting > >>> > > >>> > - Integration in test environment > >>> > > >>> > - Integration in system > >>> > > >>> > I'm currently using it as a debugging tool. It can also be useful to > >>> > monitor transactions while interacting with system in real time. I’m > >>> > thinking about integrating this tool in automated tests. > >>> > > >>> > Code and instructions are on github: > >>> > > >>> > https://github.com/alenca/zklogtool > >>> > > >>> > I would appreciate any feedback. > >>> > > >>> > Thanks > >>> > >> > >> > > > > >
