Miguel Correia commented on ZOOKEEPER-816:

Several comments:

Aspects: ah, these aspects. I always though of it as a software development 
process, not as providing a solution for compiling different versions of the 
code. I actually looked if Java already had something similar like the C 
preprocessor but didn't find it (I'm afraid I'm still from the pre-Java era). 
But it seems like a great solution.

Binary traces: I thought about that solution but was forgetting it due to idea 
of not messing with the server code thus using the actual ZK traces. However, 
together with the need of extending those traces and the idea of using AspectJ, 
it seems a neat solution.

Disk overhead: I was forgetting this problem. Using some kind of ring buffer 
seems to be a solution but we are actually interested in understanding 
failures, so keeping the info in memory doesn't seem to be a good idea (the 
failure may be too radical and we lose the info). 

> Detecting and diagnosing elusive bugs and faults in Zookeeper
> -------------------------------------------------------------
>                 Key: ZOOKEEPER-816
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-816
>             Project: Zookeeper
>          Issue Type: New Feature
>            Reporter: Miguel Correia
>            Priority: Minor
> Complex distributed systems like Zookeeper tend to fail in strange ways that 
> are hard to diagnose. The objective is to build a tool that helps understand 
> when and where these problems occurred based on Zookeeper's traces (i.e., 
> logs in TRACE level). Minor changes to the server code will be needed.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to