awesome! that would be great ivan. i'm sure pat has some more concrete suggestions, but one simple thing to do is to run the unit tests and look at the log messages that get output. there are a couple of categories of things that need to be fixed (this is in no way exhaustive):

1) messages that have useful information, but only if you look in the code to figure out what it means. there are some leader election messages that fall into this category. it would be nice to clarify them. 2) there are error messages that really aren't errors. when shutting down there are a bunch of errors that are expected, but still logged, for example.
3) misclassified error levels

welcome aboard!


On 03/29/2010 10:07 AM, Ivan Kelly wrote:

Im going to be using Zookeeper quite extensively for a project in a
few weeks, but development hasn't kicked off yet. This means I have
some time on my hands and I'd like to get familiar with zookeeper
beforehand by perhaps writing some tools to make debugging problems
with it easier so as to save myself some time in the future. Problem
is I haven't had to debug many zookeeper problems yet, so I don't know
where the pain points are.

So, without further ado,
        - Are there any places that logging is deficient that sorely needs
        - Could current logs be improved any amount or presented in a more
readable fashion?
        - Would some form of log visualisation be useful (for example in
something approximating a sequence diagram)?

Feel free to suggest anything which the list above doesn't allude to
which you think would be helpful.


Reply via email to