[
https://issues.apache.org/jira/browse/ZOOKEEPER-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889647#action_12889647
]
Miguel Correia commented on ZOOKEEPER-816:
------------------------------------------
The idea behind using ZK's log4j logs was to modify ZK's server-side code as
less as possible. ZK is used in critical applications so a design principle
that we are using is to avoid anything that may impact its reliability. In that
sense, ZK's WAL is probably not a good option as it is specially critical for
the correct operation of ZK.
Another option that occurred to me was to create another log4j logger, which
would be used specifically for logging the traces we need. Either if we use the
original log4j logger or a new one, we can improve the performance using the
same mechanisms that are used to make the WAL efficient.
In relation to Aspects, I didn't understand what do you mean. Can you give me
some pointers?
Thanks!
> 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.
